|Anonymous | Login||12-16-2019 09:43 UTC|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Simple Details [ Jump to Notes ]||[ View Advanced ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0004677||[Squeak] Morphic||minor||always||09-01-06 03:36||10-09-07 02:59|
|Summary||0004677: Collapsing world works but uncollapsing it causes an out of memory crash.|
In a fresh squeak ( I used 7055)
in a workspace evaluate:
World collapse .
( a collapsed Window named "world" will show up.)
The world will still exist. Clicking will bring the world menu up etc.
Now press the uncollapse button on the Window named "world".
The button changes color. Nothing happens for a long time (clicks don't get notices etc.) (The cursor still moves and I can access the non squeak parts of my operating system.)
Eventually the out of memory simple text window (Classic.out) comes up to inform me I have run out of memory.
I haven't looked but this probably will crash any squeak.
I am running on a iMac G3 in OS9.1. Vm is Squeak 3.8.9b7 Classic.
Though it may be a clue to a major problem, this is a minor urgency bug.
I ran into it while doing other things and found it to be simply and easily reproducible in a fresh squeak. Reported here for the fearless, intrepid, curious bughunter to persue.
As you can see there was plenty of memory. So something is looping to use it all up.
The following is the Classic.out output.
out of memory
163928716  in SystemDictionary>handleUserInterrupt
163928808  in BlockContext>newProcess
|There are no notes attached to this issue.|
|09-01-06 03:36||wiz||New Issue|
|10-09-07 02:59||matthewf||Relationship added||child of 0005124|
| Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
33 total queries executed.|
27 unique queries executed.