Medium Description
Bug in Jetty can cause OOME - java.lang.OutOfMemoryError: requested 239288 bytes for Chunk::new. Out of swap space?
Native heap is leaked by the JVM if you do not explicitly close of gzip streams. Jetty has this outstanding bug which shows it is affected by this problem:
The stack trace shows:
Caused by: java.lang.OutOfMemoryError at java.util.zip.Deflater.init(Native Method) at java.util.zip.Deflater.<init>(Deflater.java:123) at java.util.zip.GZIPOutputStream.<init>(GZIPOutputStream.java:46) at org.mortbay.servlet.GzipFilter$GzipStream.doGzip(GzipFilter.java:481) at org.mortbay.servlet.GzipFilter$GzipStream.<init>(GzipFilter.java:373) at org.mortbay.servlet.jetty.IncludableGzipFilter$IncludableGzipStream.<init>(IncludableGzipFilter.java:62) at org.mortbay.servlet.jetty.IncludableGzipFilter$IncludableResponseWrapper.newGzipStream(IncludableGzipFilter.java:53) at org.mortbay.servlet.GzipFilter$GZIPResponseWrapper.getOutputStream(GzipFilter.java:297) at javax.servlet.ServletResponseWrapper.getOutputStream(ServletResponseWrapper.java:112) at com.cenqua.fisheye.web.CommitActivityChartAction.processChart(CommitActivityChartAction.java:158)
We should try and work around it, or upgrade to a later version of Jetty if its fixed there.
