Catching java.lang.OutOfMemoryError?

by

There are a number of scenarios where you may wish to catch an OutOfMemoryError and in my experience (on Windows and Solaris JVMs), only very infrequently is OutOfMemoryError the death-knell to a JVM.

There is only one good reason to catch an OutOfMemoryError and that is to close down gracefully, cleanly releasing resources and logging the reason for the failure best you can (if it is still possible to do so).

In general, the OutOfMemoryError occurs due to a block memory allocation that cannot be satisfied with the remaining resources of the heap.

When the Error is thrown the heap contains the same amount of allocated objects as before the unsuccessful allocation and now is the time to drop references to run-time objects to free even more memory that may be required for cleanup. In these cases, it may even be possible to continue but that would definitely be a bad idea as you can never be 100% certain that the JVM is in a reparable state.

Demonstration that OutOfMemoryError does not mean that the JVM is out of memory in the catch block:

private static final int MEGABYTE = (1024*1024);
public static void runOutOfMemory() {
    MemoryMXBean memoryBean = ManagementFactory.getMemoryMXBean();
    for (int i=1; i <= 100; i++) {
        try {
            byte[] bytes = new byte[MEGABYTE*500];
        } catch (Exception e) {
            e.printStackTrace();
        } catch (OutOfMemoryError e) {
            MemoryUsage heapUsage = memoryBean.getHeapMemoryUsage();
            long maxMemory = heapUsage.getMax() / MEGABYTE;
            long usedMemory = heapUsage.getUsed() / MEGABYTE;
            System.out.println(i+ " : Memory Use :" + usedMemory + "M/" +maxMemory+"M");
        }
    }
}

Output of this code:

1 : Memory Use :0M/247M
..
..
..
98 : Memory Use :0M/247M
99 : Memory Use :0M/247M
100 : Memory Use :0M/247M

If running something critical, I usually catch the Error, log it to syserr, then log it using my logging framework of choice, then proceed to release resources and close down in a clean fashion. What’s the worst that can happen? The JVM is dying (or already dead) anyway and by catching the Error there is at least a chance of cleanup.

The caveat is that you have to target the catching of these types of errors only in places where cleanup is possible. Don’t blanket catch(Throwable t) {} everywhere or nonsense like that.

More Related Contents:

  1. NumberFormatException not wrking java
  2. Error java.lang.OutOfMemoryError: GC overhead limit exceeded
  3. Is it expensive to use try-catch blocks even if an exception is never thrown?
  4. “java.lang.OutOfMemoryError : unable to create new native Thread”
  5. How do you implement a re-try-catch?
  6. Is it possible to catch out of memory exception in java? [duplicate]
  7. Program freezes during Thread.sleep() and with Timer
  8. Problem with “scopes” of variables in try catch blocks in Java
  9. How to load a large xlsx file with Apache POI?
  10. java.lang.OutOfMemoryError: Java heap space in Maven
  11. Processing large xlsx file
  12. Unable to execute dex: GC overhead limit exceeded in Eclipse
  13. Java if vs. try/catch overhead
  14. Java try/catch/finally best practices while acquiring/closing resources
  15. Java io ugly try-finally block
  16. EOFException – how to handle?
  17. Throws or try-catch
  18. Java: Unable to create new native thread
  19. Try-with-resources equivalent in Java 1.6
  20. Horrendous performance & large heap footprint of Java 8 constructor reference?
  21. Java try/catch performance, is it recommended to keep what is inside the try clause to a minimum?
  22. Should try…catch go inside or outside a loop?
  23. Java – shutting down on Out of Memory Error
  24. Catching an exception that is nested into another exception
  25. Why is declaration required in Java’s try-with-resource
  26. java.lang.OutOfMemoryError: Java heap space with NetBeans
  27. Java InputMismatchException
  28. “java.lang.OutOfMemoryError: PermGen space” in Maven build [duplicate]
  29. Java heap space in netbeans.. but I’ve increased the heap size already!
  30. How to avoid OOM (Out of memory) error when retrieving all records from huge table?

Leave a Comment