Issue 3646 in pharo: Improve LowSpace handling

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 3646 in pharo: Improve LowSpace handling

pharo
Status: Accepted
Owner: [hidden email]
Labels: Type-RequestForEnhancement

New issue 3646 by [hidden email]: Improve LowSpace handling
http://code.google.com/p/pharo/issues/detail?id=3646


- Smalltalk memoryHogs
should use weak container,
to prevent hanging references.

- add the way to hook into default low space condition handling, instead of  
unconditionally go invoke:
        UIManager default lowSpaceWatcherDefaultAction: preemptedProcess


Reply | Threaded
Open this post in threaded view
|

Re: Issue 3646 in pharo: Improve LowSpace handling

pharo

Comment #1 on issue 3646 by [hidden email]: Improve LowSpace handling
http://code.google.com/p/pharo/issues/detail?id=3646

Also, i think that mechanism which suspends the process which made the last  
memory allocation attempt is useless,  because
there is no any guarantees that exactly given process causing memory  
overflow due to some runaway allocation, instead of some other one which  
runs in parallel.



Reply | Threaded
Open this post in threaded view
|

Re: Issue 3646 in pharo: Improve LowSpace handling

pharo

Comment #2 on issue 3646 by [hidden email]: Improve LowSpace  
handling
http://code.google.com/p/pharo/issues/detail?id=3646

"And you are right, there is no way to hook into low space watcher to
include some custom handling. So, this is a work to do."

see  
http://lists.gforge.inria.fr/pipermail/pharo-project/2011-February/041178.html
for the whole discussion