StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Are you positive you closed the stream and invoked <code>end</code> on the deflater? I'm sorry if this is a simplistic suggestion you've already tried, but there were a lot of complaints about a memory leak when using <code>Deflater</code> when not immediately invoking <code>end</code> on it, for example:</p> <ul> <li><a href="http://www-01.ibm.com/support/docview.wss?uid=swg21227106" rel="nofollow noreferrer">http://www-01.ibm.com/support/docview.wss?uid=swg21227106</a></li> <li><a href="http://bugs.sun.com/view_bug.do?bug_id=6734186" rel="nofollow noreferrer">http://bugs.sun.com/view_bug.do?bug_id=6734186</a> (1.5)</li> <li><a href="https://stackoverflow.com/questions/6274696/excessive-memory-use-by-java">excessive memory use by java</a></li> <li><a href="http://bugs.sun.com/view_bug.do?bug_id=4797189" rel="nofollow noreferrer">http://bugs.sun.com/view_bug.do?bug_id=4797189</a></li> <li><a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6293787" rel="nofollow noreferrer">http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6293787</a></li> <li><a href="http://kohsuke.org/2011/11/04/quiz-answer-memory-leak-in-java/" rel="nofollow noreferrer">http://kohsuke.org/2011/11/04/quiz-answer-memory-leak-in-java/</a></li> </ul> <p>The root cause is apparently that the collector is not able to keep up with the application when memory used by native elements is involved. That also explains the behavior you are seeing when profiling: the memory is ready to be reclaimed, but just isn't reclaimed quickly enough.</p> <p>Since you wrote you don't use a <code>Deflator</code> directly but through Apache Thrift, try to identify which method in that library is responsible for ending the deflator, and made sure you invoked that method.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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