I propose to enable again that on image startup the timer scheduling process is restarted.
https://pharo.fogbugz.com/default.asp?10994 https://pharo.fogbugz.com/default.asp?10545 I am not fully sure of the implications, but it used to be there before and I have less troubles when it is enabled ;) On 2013-06-20, at 10:02, Marcus Denker <[email protected]> wrote: > Hi, > > I think we should for now just kill them when building the image, I will > check. > > On Jun 20, 2013, at 9:56 AM, Clément Bera <[email protected]> wrote: > >> Hello, >> >> These processes are due to the new integration testing process. This new >> process was introduced in Pharo 3.0 alpha, and we found the bug and fixed >> it. >> Recently we backport the new integration process to Pharo 2.0 and seemingly >> it created the same bug but since we read your mail we were not aware of it. >> We need to backport the fix. >> We will fix that within a few days. >> >> As a workaround, you can just kill these processes in your image for now ... >> >> Thanks for reporting the issue, >> >> >> >> >> 2013/6/20 NISHIHARA Satoshi <[email protected]> >> There are 30 over processes are running at startup, Pharo-20607.image. >> >> <NDOWS-1252?B?vIgyMDEzLTA2LTIwIDEzLjE5LjU277yJLnBuZw=.png> >> >> regards. >> >> -- >> -- >> "NISHIHARA Satoshi" >> [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] >> >> >> >> -- >> Clément Béra >> Mate Virtual Machine Engineer >> Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq >
