On 12 April 2013 23:14, phil@highoctane.be <phil@highoctane.be> wrote:
+1. No clue either. But discovered the terminate process shortcut to kill them faster...
Coping over solving ...
One of the "solutions" i proposed is to rewrite the code and get rid of "nano-second" """"synchronization""" of date and time with system clock because a) there is no real users of it (to my knowledge) b) you cannot have precision higher than precision of system primitive we're using, which is in millisecond range.. c) i see it completely stupid to try to do magic tricks trying to be smart and squeeze more precision than underlying system can offer. For that: i would use non-existing-yet primitive, lets say: <primitive: 'NanoSecondSystemTimeFrom1Jan1900' module: ''> and since this primitive fails, because it don't exists, the fallback will use old primitive which currently in VM.. because (repeating again) doing black magick and trickery in image buys us nothing and only serves as a source of bugs. -- Best regards, Igor Stasenko.