Bug in Kernel: 1. Pharo Image
• You are subscribed to this case
It is not a Pharo bug. Just a concurency issue: loop is not niled fast enough in the loop process of TimerScherduler>>startUp compared to the startup made in doStartUp. so loop is still not nil when the startup begin.
A solution is to do in TimerScheduler >> startLoop
loop := nil. processExited signal.
instead of
processExited signal. loop := nil.
Status changed:
Work Needed
Resolved (Fix Review Needed)