Yes that is a very nasty bug, and I think it is not that easy to fix. If you really want to fix it we will have to fiddle with the whole startup mess. see comments in: https://code.google.com/p/pharo/issues/detail?id=7129 strangely enough it was introduced in 20460! image 20459 worked without problems. looking at the diffs doesn't reveal anything that could immediately cause the bug: 20459: https://github.com/pharo-project/pharo-core/commit/b83bda681530692a08efa4309... 20460: https://github.com/pharo-project/pharo-core/commit/16fe676a4ff25d720340ac8c4... 20461: https://github.com/pharo-project/pharo-core/commit/382d4c637b5f433edcb4d99d0... 20462: https://github.com/pharo-project/pharo-core/commit/2aece46a9ac922a81e931309c... the most probable change happened in 20462, but I am not sure if that is the cause. On 2013-02-11, at 14:54, Sven Van Caekenberghe <sven@stfx.eu> wrote:
I have seen this before, and it is probably related to other problems that we have been seeing lately:
Basically the whole initialization of DateAndTime (class side) goes wrong.
Could this have something to do with Delay problems ?
Some time ago, there were some Delay changes, right ?
yeah, in the case the image hangs, there are always a couple (5 - 10) processes hanging in the image due to the DateAndTime offset initialization stuff. So my guess is that by making that lazily initialized we could get rid of the bug. maybe you can dig into that direction, I don't have much time at hand these days ;)