On Sun, Jul 17, 2016 at 6:46 AM, Ben Coman <btc@openinworld.com> wrote:

��

Do you have some test code or a test image I could run to reproduce
the problem?

The problem is that I cannot reproduce it immediately. It takes me some days and likely some image save and start again until I reproduce it.��

��

Now I have one thing for you to try.�� In the move of DelaySchedulerXxx
from milliseconds to microseconds, the code for dealing with clock
wrap-around was removed, but I wonder if it was also covering clock
jitter as a side effect.�� Could you try again the SpinScheduler but
restore this code...

>From handletTimerEvent...
�� "Check for clock wrap-around."
�� millisecondNowTick < activeDelayStartTime ifTrue: [
�� �� "clock wrapped"
�� �� self saveResumptionTimes.
�� �� self restoreResumptionTimes ].
�� activeDelayStartTime := millisecondNowTick.

>From runTimerEventLoop...
�� Time millisecondClockValue < millisecondNowTick
�� �� ifTrue:[ timingSemaphore signal ]. "retry"

>From startup...
�� ��activeDelayStartTime := Time millisecondClockValue.

OK, I put back the code into the spin scheduler. Then I kept using milisecond one until I finished the changes. Then I saved image and switch to spin one: the image hungs. I cannot even interrupt it. I attach my modifications.��

Do they look correct?��