Tim Ellison wrote:
Geir Magnusson Jr. wrote:
I think that it's totally unreasonable to have no upper bound on stack
size. A Java virtual machine should never be able to hose a machine by
sucking in all memory...
yeah, like those rotten C programs. You are damned if you do and damned
if you don't, since you'll upset people who hit any arbitrary limit that
you set on the stack size too. As we have seen, current impls do limit.
Clearly the "suck all memory until the box turns over and wiggles it's
feet in the air" setting isn't needed by anyone. Is there some
reasonable heuristic based on heap defaults or settings?
geir
Regards,
Tim
