2008/11/18 Marcus Denker <[EMAIL PROTECTED]>: > > On 18.11.2008, at 17:11, Simon Denier wrote: > >> If I dowload the latest 10156 image, do a ScriptLoader loadOB, save it as >> new image, quit and then relaunch the new image, my new image is unusable >> because almost unresponsive: something is eating 100% CPU time. >> >> - problem is the same if I upgrade to 10157 >> - however there seems to be no problem if I just continue to work in the >> image without quitting. >> >> It's a weird behaviour. >> > > Yes, I will undo some process related changes... maybe removing Process from > the specialObjectsArray was a dunb idea ;-) > I will put it back in. > Don't be so haste :) I'd rather try to reproduce the problem and find solution.
a 100% cpu hog at startup time could be a problem with Delays, or different semaphores which has dropped during #clearExternalObjects but not correctly reinstantiated again at following startup phase. > Marcus > > -- > Marcus Denker -- [EMAIL PROTECTED] > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
