2

I have been working on this project on Java with multiple modules. Since quite some time, I have been occasionally getting "java: Out Of Memory" error! I am pretty new to this 'popular' error and wanted to know the general approach to solve such errors.
Also, are there standard tools accepted by the industry to help figure out the cause of such errors?
The modules in my project include every minute polling from a third party (using web service), multi-threading among other things. However, this is just a pointer and I seek a general approach and not something very specific to my project.
Thanks.

Leo
  • 187
  • 6
  • 19

5 Answers5

3

Sometimes you just have an class that uses a lot of memory and you need to increase the heap size or make a more space-efficient algorithm. Other times it is a leak and you need to deference objects.

  1. Run jvisualvm (it's included in the JDK).
  2. Connect to your process and try if you can to recreate the out-of-memory error while keeping an eye on the heap size.
  3. Perform a heap dump when the memory grows large. Search for the largest objects by size - often that will give you the culprit class.
  4. Look at the dependencies to see what is holding a references. If it is a memory leak make sure to dereference unneeded objects.
Garrett Hall
  • 29,524
  • 10
  • 61
  • 76
2

Also, are there standard tools accepted by the industry to help figure out the cause of such errors?

Yes, there are memory profilers such as VisualVM and YourKit. I use the latter extensively, for both CPU and memory profiling, and find it extremely useful. To get some idea of what it's capable of, take a look at this page: link.

NPE
  • 486,780
  • 108
  • 951
  • 1,012
1

If you can't increase the available memory you have to consume less.

Don't keep references to Objects that you don't need at the time of execution (like data you can reload dynamically) and if necessary redesign your flow (e.g. don't process all objects in parallel and do it sequentially) to require less memory at that time. The garbage collection should do the rest for you.

Especially if you load big data objects into memory consider to use a streaming approach if possible. E.g. you don't need to load a whole file into memory if you want to search through it. You can just step through it.

Besides architectural problems you can also have leaks: keeping unintentional references to objects you don't need anymore. Since they are referenced, the garbage collector can't free the memory and you run out of memory at some point. That is probably the #1 reason for OutOfMemoryExceptions and it usually has to do with static references since classes and therefore the statics are usually not unloaded after the first time you touch a class. The internet has many articles on finding / fixing those, e.g. How to Fix Memory Leaks in Java

one tool I know of is MAT

Community
  • 1
  • 1
zapl
  • 63,179
  • 10
  • 123
  • 154
0

You likely have a memory leak. Finding it is a challenge. Netbeans has some tools to help you profile the VM . You can profile your project and view men usage while it runs. Apache JMeter is also available as a plug-in or you can run it on its own. JMeter.apache.org

Thorn
  • 4,015
  • 4
  • 23
  • 42
0

If you get OOM too often, then start java with correct options, get a heap dump and analyze it with jhat or with memory analyzer from eclipse (http://www.eclipse.org/mat/)

 -XX:+HeapDumpOnOutOfMemoryError   -XX:HeapDumpPath=<path to dump file>
kofemann
  • 4,217
  • 1
  • 34
  • 39