Am 15.10.16 um 20:00 schrieb Paul DeBruicker:
I have no idea why it happens but sometimes OSProcess resumes working after doing a
OSProcessAccessor initialize.
in a workspace.....
Hope this helps
It did help *me*, thanks for sharing this on the list. I just had the same issue (like described from Hilaire below) in a new Pharo 6.1 image. It locked the image and left a zombie process. "OSProcessAccessor initialize" did the trick. Cheers, Andreas
HilaireFernandes wrote
Hello,
On Pharo4, when I type the command:
OSProcess waitForCommand: 'ls'
it locks the image, I can get back control with [Alt]-.
With the same image and VM, this command was previously working, even called from a Seaside component.
Any idea?
Thanks
Hilaire
-- Dr. Geo http://drgeo.eu
-- View this message in context: http://forum.world.st/OSProcess-lock-image-tp4918923p4918935.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
-- Andreas Brodbeck www.mindclue.ch