pawel.veselov at gmail.com
Wed Jul 14 15:08:17 UTC 2010
On Wed, Jul 14, 2010 at 6:25 AM, Florian Weimer <fweimer at bfk.de> wrote:
> * Pawel Veselov:
> > The fact that I catch any Throwable around the code that threw the
> > OOM error didn't particularly help. The error was logged, but the
> > timer thread still died.
> By definition, a VM which throws an Error (or even
> VirtualMachineError) is unstable and needs to be restarted. The
> description of VirtualMachineError makes that pretty clear. You
> cannot even know that the thread that triggers such exceptions is
> responsible for their actual cause.
Considering the fact that its probably unreasonable to ask the user
code to catch the VME everywhere, or that VME may not even reach the user
should we have something like -XX:DieOnVME=<process_error_code> ?
Or global VM VME handler that has certain amount of pre-reserved memory,
which gets executed before VM terminates, and can be configured?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the core-libs-dev