Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Since the extra memory is not showing in MAT it's hard to know what to suggest. My apologies if some (or even most) of this is things you already know, I've just tried to pull together everything I could think of.</p> <p><strong>FindBugs</strong></p> <p>FindBugs is a static analysis tool that will scan your code looking for common anti-patterns and problems and giving you a nice report on them. It does pick up on a lot of causes of potential memory and resource leaks.</p> <p><strong>Manual dump</strong></p> <p>You could try using something like jmap or visualvm to take a heap dump for analysis manually and see if you get different results from letting eclipse do it:</p> <p><a href="http://docs.oracle.com/javase/1.5.0/docs/tooldocs/share/jmap.html" rel="nofollow">http://docs.oracle.com/javase/1.5.0/docs/tooldocs/share/jmap.html</a></p> <p><a href="http://java.dzone.com/articles/java-heap-dump-are-you-task" rel="nofollow">http://java.dzone.com/articles/java-heap-dump-are-you-task</a></p> <p><strong>Analyzer Quirks</strong></p> <p>The memory analyzer FAQ:</p> <p><a href="http://wiki.eclipse.org/MemoryAnalyzer/FAQ" rel="nofollow">http://wiki.eclipse.org/MemoryAnalyzer/FAQ</a></p> <p>says:</p> <blockquote> <p>Symptom: When monitoring the memory usage interactively, the used heap size is much bigger than what MAT reports.</p> <p>During the index creation, the Memory Analyzer removes unreachable objects because the various garbage collector algorithms tend to leave some garbage behind (if the object is too small, moving and re-assigning addresses is to expensive). This should, however, be no more than 3 to 4 percent. If you want to know what objects are removed, enable debug output as explained here: MemoryAnalyzer/FAQ#Enable_Debug_Output</p> <p>Another reason could be that the heap dump was not written properly. Especially older VM (1.4, 1.5) can have problems if the heap dump is written via jmap. </p> </blockquote> <p>Enabling debug output will allow you to see what is going on there and confirm there is nothing odd in that area.</p> <p><strong>Some of these tips may be relevant</strong></p> <p><a href="http://eclipsesource.com/blogs/2013/01/21/10-tips-for-using-the-eclipse-memory-analyzer/" rel="nofollow">http://eclipsesource.com/blogs/2013/01/21/10-tips-for-using-the-eclipse-memory-analyzer/</a></p>
    singulars
    1. This table or related slice is empty.
    1. POFinding Java memory leak when not all used heap is reachable from threads
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USTim B
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, these are all very good things to explore... At least I've got a few more directions to explore
      singulars
      1. PO
      1. USVoidPointer
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload