_Jv_SetMaximumHeapSize

Sun Sep 21 12:15:00 GMT 2003

Maybe setting maximum heap size could be dangerous too, just as setting ulimits (what
if the program *really* needs more memory...?).
What would be your take on what the Python people seem to do somehow?
They seem to garbage-collect but make sure as well that reference counting
de-allocates memory as early as possible. (I understand that reference counting in
itself carries both a memory as well as a performance penalty).
On the other side, it would increase the sense of control that is lacking now when
one observes evergrowing memory usage (even when it is justified) without the ability
to do something about it... Or maybe the whole idea is silly for some other reason I
am not aware of?