Summary: | Improve JreMemoryLeakPreventionListener against leak caused by sun.java2d.Disposer | ||
---|---|---|---|
Product: | Tomcat 6 | Reporter: | Michał Politowski <mpol> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | default | ||
Hardware: | PC | ||
OS: | Linux |
Description
Michał Politowski
2011-08-19 14:41:36 UTC
Which daemon thread? Is this the same as bug #51688? I do not think so. It is a thread named "Java2D Disposer", created in the static initializer of the sun.java2d.Disposer class. Can you post minimal code to cause this thread to be created? I've just added a fix for that other, somewhat related, bug and I'd be happy to add this as well. The exact code that causes it in the webapp at hand is a sun.java2d.Disposer.getQueue() call somewhere in the standard JRE library, but actually just anything that loads the class, even Class.forName("sun.java2d.Disposer"), is enough. Fixed in trunk, 7.0.x branch. Will be included in 7.0.22 onward. |