This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 70172

Summary: Leaking classloader instances
Product: javaee Reporter: _ rkubacki <rkubacki>
Component: JSP ParserAssignee: Anton Chechel <manowar>
Status: RESOLVED WORKSFORME    
Severity: blocker CC: gtzabari, issues, pjiricka, ppisl
Priority: P3 Keywords: PERFORMANCE
Version: 5.x   
Hardware: All   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Bug Depends on:    
Bug Blocks: 70052    

Description _ rkubacki 2005-12-09 19:42:54 UTC 
dev build from Dec 8, JDK 1.6.0_b62

After some editing of JSP files I close them all and closed the project but
there are still 35 instances of
org.netbeans.modules.web.jspparser_ext.WebAppParseSupport$ParserClassLoader
referenced from log factory of commons logging -

Static reference from org.apache.commons.logging.LogFactory.factories (from
class org.apache.commons.logging.LogFactory) :
--> java.util.Hashtable@0x8805d6a8 (40 bytes) (field table:)
--> [Ljava.util.Hashtable$Entry;@0x8872f968 (196 bytes) (Element 42 of
[Ljava.util.Hashtable$Entry;@0x8872f968:)
--> java.util.Hashtable$Entry@0x889e2af0 (24 bytes) (field key:)
-->
org.netbeans.modules.web.jspparser_ext.WebAppParseSupport$ParserClassLoader@0x889e4930
(67 bytes)

I am not clear how dangerous it is. At least there are 0 loaded classes so we do
not fill perm gen but still we are leaking in Java heap.
Comment 1 Petr Pisl 2005-12-20 09:42:45 UTC 
The impact seems to be small. Should be fixed in the next release.
Comment 2 Petr Pisl 2007-10-18 13:31:38 UTC 
This is still there.
Comment 3 Jiri Prox 2008-04-11 01:13:41 UTC 
moving opened issues from TM <= 6.1 to TM=Dev
Comment 4 Anton Chechel 2011-04-11 14:25:20 UTC 
Profiled this. Issue is no longer reproducible.
There is no references from LogFactory anymore. After editing few JSP pages there are always only 2 references from RequestProcessor.