I noticed on the limitations page on the wiki that the OOM has not stacktrace because it's pre-allocated.

I've always thought it would be nice to have the stack trace - I know that in some environments, people actually catch and deal with OOMs in long running procs.

I think it would be cool if we could figure out a way to provide stack trace (I realize the obvious problems...) and let people use that info for making go/die decisions.

Just a thought.

geir

Reply via email to