On Apr 21, 2012, at 7:18 PM, Stéphane Ducasse wrote:
I guess that we have a showstopper for 1.4 :) Because when I take 1.4 and modify a method in the implementor pane I can also freeze the systemâ¦. I will repeat it to be sure.
In fact this is not related to the implementor but more a problem with morph property like resist to delete or something like thatâ¦. Investigating
Stef
On Apr 21, 2012, at 2:01 AM, phil@highoctane.be wrote:
To freeze 1.4 on Win XP SP3, you can try this one out:
| tm border | tm := TextMorph new. tm contentsWrapped: ''; extent: 100 @ 20. "this is the important stuff" (border := AlignmentMorph newRow) position: 200 @ 200; borderWidth: 1; borderColor: Color black; hResizing: #shrinkWrap; vResizing: #shrinkWrap; addMorph: tm. "this just makes the TextMorph easier =to see" World addMorph: border.
Then fill in the TextMorph with some text and newlines.
Then call the halos and resize the right corner for a while, especially letting it go out of screen at the bottom.
The system will come unresponsive, not obey Cmd-. etc.
Sometimes it comes back to life but most of the time I've got to kill the process.
CogVM or StackVM make no difference.
Maybe there is a huge GC going on but there is no memory display thing (manuia) anymore in 1.4 so I can't tell.
Hope it helps.
Phil
2012/4/20 Paul DeBruicker <pdebruic@gmail.com>
Janko Mivšek wrote
After Ctrl-C in command prompt there is no new PharoDebug.log.
Instead of Crtl-C do you get anything if you find the process and kill it with:
kill -s SIGUSR1 <pid>
? (assuming you're using Cog )
-- View this message in context: http://forum.world.st/Unresponsive-1-4-image-tp4574693p4575089.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve"
Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil@highoctane.be | Web: http://philippeback.eu | Blog: http://philippeback.be
High Octane SPRL rue cour Boisacq 101 1301 Bierges