Here is something I found by accident... If I run my app, then close it, then save/exit the image, then open the image again, edit my application class to add a new instance variable, then save the change â Pow! â I get about a dozen debugger pop-ups saying "#wait was sent to nil". What this tells me (and you may correct me if I'm wrong), the VM still has a thread running that is sending #wait messages to my application *which has already shutdown*. This can't be good, but whether this is related to the segmentation fault is anybody's guess at this point. Stephane Ducasse-3 wrote
Thanks for reporting. I hope that in Pharo 70 we will get rid of the FreeType pluging.
Stef
On Thu, Jun 1, 2017 at 3:30 PM, horrido <
horrido.hobbies@
> wrote:
I downloaded Pharo 6.0 but used the same Spur VM (which I presume is still the latest for Raspberry Pi): http://files.pharo.org/vm/pharo-spur32/linux/armv6/pharo-linux-ARMv6- 201705051953-b8db6de.zip
It crashed, too.
Denis Kudriashov wrote
2017-05-31 17:57 GMT+02:00 horrido <
horrido.hobbies@
>:
I'm using Pharo 5.0
I test it with Pharo 6 (latest image and VM) and have no problem. Could you check it too?
-- View this message in context: http://forum.world.st/Morphic- or-forking-bug-tp4948727p4948818.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
-- View this message in context: http://forum.world.st/Morphic-or-forking-bug-tp4948727p4948911.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.