Comment #3 on issue 5608 by
[hidden email]: ReleaseTest
#testObsoleteClasses fails
http://code.google.com/p/pharo/issues/detail?id=5608I've seen this too. I think there is something in the image that is
hanging on to Reference, but (somehow) gets cleaned up during startup or
GUI initialisation.
If I run "PointerExplorer openOn: (SystemNavigation default obsoleteClasses
first)" in a startup script, I get an explorer window with a few
references, but I can't explore any further as the references are cleaned
up by the time the GUI starts displaying/responding :(
I've attached a script that opens a PointerExplorer and expands all the
elements to a particular level. Change the 5 to whatever you want. Note
that numbers > 5 take loooooong on my computer. Hopefully you have
something faster.
Also, note the #OnceOnly wrapper in the script - startup scripts are
currently being run 8 times for me (on Linux), but I'll submit another
issue for that once I have it characterised better.
Attachments:
test2.st 406 bytes
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker