java out of memory then exit

Question

I have a piece of software that has to analyze big files. Constraining the input or giving infinite memory is not an option, so I have to live with flying OOMEs. Because the OOME only kills the Thread, my software runs in some crappy state.

From outside everything looks okay because the process is running but on the inside it's braindead.

I would like to pull the plug on it. But how can I do this?

Catching a OOME does not guranteee that the next line of code will be executed. e.g System.exit(9). So the JVM has to notice OOME and destory itself.

Is their some vm option for this?

*"Catching a OOME does not guranteee that the next line of code will be executed."* You have a reference for that? — aioobe, May 17 '11 at 06:46

score 8 · Answer 1 · answered May 17 '11 at 06:56

8

When you get an OOME you can be very low on memory and logging doesn't always work. One way around this is to have a shutdown method which holds some memory it doesn't release until its shutting down.

e.g.

 private static byte[] lastResort = new byte[256*1024];
 public static void handleOOME(OutOfMemoryError oome) {
     lastResort = null;
     try {
        LOG.fatal("Dying after ", oome);
     } finally {
        System.exit(-1);
     }
  }

answered May 17 '11 at 06:56

Peter Lawrey

525,659
79
751
1,130

2

Interesting approach! Do you have that in production somewhere? – Joachim Sauer May 17 '11 at 07:27
1

Brave, exotic, outrageous :p – Yngve Sneen Lindal Apr 12 '13 at 10:41
@JoachimSauer I did use this in production with 64KB reserved. – Peter Lawrey Apr 12 '13 at 11:03

score 3 · Answer 2 · answered Dec 23 '18 at 13:04

You can use -XX:+ExitOnOutOfMemoryError - supported by Java 8 update 92.

You can also use -XX:+CrashOnOutOfMemoryError to get the core dump for further investigation.

You can also use -XX:+HeapDumpOnOutOfMemoryError to generate a heap dump on OOME for further investigation.

Source: this and this.

Stephen C · Answer 3 · 2011-05-17T07:05:15.403

2

So the JVM has to notice OOME and destroy itself. Is their some vm option for this?

No there is not.

However, I have to question your assumption that you cannot catch an OutOfMemoryError and and immediately call System.exit() in the exception handler.

In practice it should work. The only potential problem is if you have called Runtime.setRunFinalizersOnExit(true) ... and even that is ignored if you exit with a non-zero exit status.

(The caveat about catching OOME's and other random Error exceptions is that the JVM may not be in a fit state to continue executing. But calling System.exit(nonzero) ain't doing that!)

edited May 17 '11 at 07:05

answered May 17 '11 at 06:57

Stephen C

698,415
94
811
1,216

It does work, I've written a Swing program that catches an OutOfMemoryError then puts a message to the screen about it. – Adam May 17 '11 at 07:01
The act of catching an OOME several levels down the call stack **might** free enough memory for some basic logging/error handling (because the GC roots from the call stacks disappear). – Joachim Sauer May 17 '11 at 07:28
That is true, and @Peter Lawrey's answer is another approach. (I've seen it in other contexts. For instances, some JVMs do this kind of thing to reserve space for creating the OOME and its stack frames.) – Stephen C May 17 '11 at 09:21

java out of memory then exit

3 Answers3

Linked