Classloader leak in Transformer

[Iman Rahmatizadeh]

Hi, 

I've been dealing with permgen space outofmemory errors in my application, and managed to trace it to many classes with names like sun.reflect.GeneratedSerializationConstructorAccessor being created and not unloaded from my permgen space. 

These classes have in turn been loaded from hundreds of DelegatingClassLoader instances which arent also collected. Searching for references to these classloaders I found that salve's default Transformer keeps a reference to each classloader in its seenLoaders field. 

Is this a possible leak for permgen memory space ? 

p.s.  I've changed the seenLoaders to keep classloaders hashcode() instead of the actual reference and the problem seems to have gone away 

Iman 

[Igor Vaynberg]

why would you have that many classloaders? seems very strange.

-igor

> --
> You received this message because you are subscribed to the Google Groups
> "Salve" group.
> To post to this group, send email to salve...@googlegroups.com.
> To unsubscribe from this group, send email to
> salve-disc+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/salve-disc?hl=en.
>

[Iman Rahmatizadeh]

I dunno, mostly reflection stuff and methods created during object serialization in wicket. I read about it before, many say its natural using hibernate, wicket, etc.