Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Suggestions given during a meeting for finding an outOfMemoryError in Java Heap

 
Robert Silva
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Two of my fellow programmers and I along with our supervisor were in a meeting discussing an out or memory error one of our applications was having during a test of some minor changes.. One of the programmers wrote the application and the other has worked with it longer than I. I was looging for suggestions about how I could track the source of the error. The original author suggested that since I was using a different IDE than the one he programmed it with, then that could be the source of the problem. He wrote it in IntelliJ, but I'm using netbeans. The other programmer suggested that I "may have left out a curly brace". They also suggested comparing all the differences between the original app and the one that was being tested. I had spend about a week running JProfiler and narrowing down the location of the problem. To be honest, I was looking for more intelligent suggestions. I was frustrated and ended the meeting shortly after. Later that day my supervisor reprimanded me for not taking their suggestions more seriously. IMO they were useless (the suggestions, not the programmers). Does anyone else have an opinion?

Frustrated in Charleston,
 
Jerry Wegener
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It sounds like they are either unable or unwilling to assist. The IDE choice should not be an issue unless the original programmer coupled the ide right into the application. To me that isn't a good idea. The other suggstion sounds fishy. The IDE would catch that. Good luck with that one..
 
M Altaf
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Had problems with OutOfMemory errors as well.

First thing to look at is where the code broke.
The stack trace should give you an idea of where it is (i.e. line numbers or class files).

From there work out what the application was doing before the OOM happened.
Usually OOM happens when you're trying to create a data structure that is too big that there is not available memory and the JVM complains. (e.g. Really big arrays)

Get a ballpark figure on how much memory your data structures takes and see if increasing the memory of the JVM to accomodate
the memory requirements eases the OOM errors.

Hope this helps.

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic