Hi Stef,
For reporting the RFB issue I made a thread (http://forum.world.st/How-do-diagnose-image-locks-up-cpu-100-on-save-td47046...) and uploaded a Pharo 2 image to dropbox where if you execute this code:
RFBServer start Smalltalk snapshot: true andQuit: false
The image locks up using the 'pharo' VM and works fine using eliots vm. The uploaded image is Pharo-20619 with only RFB loaded.
Ok I remember. We will have a look.
The other problem I had with Pharo 2 is the ever growing image size I reported here:
http://forum.world.st/development-image-memory-use-180MB-in-Pharo-2-vs-40MB-...
Ok.
I understand this is due to some leaks involving morphs and announcers and things that are fixed in pharo 3 but not pharo 2.
Yes igor and esteban spent some times and they are probably some left. ( sadly :) doing is more difficult than doing nothing)
I have not gotten the impression that that fix will be backported, and even if it will it hasn't been yet so because of that and the RFB issue above I can't use Pharo 2 right now.
I understand. Thanks for the email.
Hope this helps and thanks for following up
Yes!
Paul