Java native memory leak due to GZIPOutputStream.close() not being called
Issue
- The Java process size grows way beyond the maximum java heap size.
- Many application threads in the following state:
java.lang.Thread @ 0x83327f10 |default task-417| 176 | 36,776 |org.jboss.modules.ModuleClassLoader @ 0x82d4e050|false
|- at java.util.zip.Deflater.init(IIZ)J (Native Method) | | | | |
|- at java.util.zip.Deflater.<init>(IZ)V (Deflater.java:171) | | | | |
|- at java.util.zip.GZIPOutputStream.<init>(Ljava/io/OutputStream;IZ)V (GZIPOutputStream.java:90) | | | | |
|- at java.util.zip.GZIPOutputStream.<init>(Ljava/io/OutputStream;)V (GZIPOutputStream.java:109) | | | | |
|- at com.example.SomeClass.write([BII)V (Unknown Source)
...
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.