ssage-
From: Chris Hegarty [mailto:[email protected]]
Sent: 22 December 2010 17:35
To: Roman Kennke
Cc: [email protected]
Subject: Re: Potential memory leak in java.util.logging.Level
On 12/22/10 02:36 PM, Roman Kennke wrote:
Hello,
I believe java.util.logging.Level is po
d time to implement a fix.
**Roman
-Original Message-
From: Chris Hegarty [mailto:[email protected]]
Sent: 22 December 2010 17:35
To: Roman Kennke
Cc: [email protected]
Subject: Re: Potential memory leak in java.util.logging.Level
On 12/22/10 02:36 PM, Roman Kennke wrot
On 12/22/10 02:36 PM, Roman Kennke wrote:
Hello,
I believe java.util.logging.Level is potentially memory leaking. This can
happen if an application defines its own subclass of Level and is loaded by its
own classloader. Level's constructor adds a reference to the new instance of
the subclass
too.
Joel
-Original Message-
From: [email protected]
[mailto:[email protected]] On Behalf Of Roman Kennke
Sent: Wednesday, December 22, 2010 9:36 AM
To: [email protected]
Subject: Potential memory leak in java.util.logging.Level
Hello,
Hello,
I believe java.util.logging.Level is potentially memory leaking. This can
happen if an application defines its own subclass of Level and is loaded by its
own classloader. Level's constructor adds a reference to the new instance of
the subclass to its 'known' ArrayList (which is a static
