Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [aspectj-users] aspectjweaver Memory leak ?

Hello Andy and thanks

It seems that you are right.

The javacore relative to the heapdump says that there are 193 classloaders

 

I don’t know if we can analyse IBM JVM heapdump  with jhat but there are other IBM  graphics tools  ( jca, ha )

 

I am not allowed to send these logs, but I can investigate with you...

 

 

Cordialement / Best regards

 

Jean-Louis Pasturel
jeanlouis.pasturel@xxxxxxxxxxxxxxxxxx


De : aspectj-users-bounces@xxxxxxxxxxx [mailto:aspectj-users-bounces@xxxxxxxxxxx] De la part de Andy Clement
Envoyé : mercredi 16 avril 2008 17:05
À : aspectj-users@xxxxxxxxxxx
Objet : Re: [aspectj-users] aspectjweaver Memory leak ?

 

Are you using multiple classloaders over the lifetime of the run?  There is an issue with weavers not disappearing because they are anchored alongside a classloader (even when the classloader has been orphaned) and bug 210470 discusses that https://bugs.eclipse.org/bugs/show_bug.cgi?id=210470 .  If that doesn't cover your situation, feel free to open a new bug where we can get to the bottom of it - but I will likely ask for your help to get to the bottom of it, I'll need a dump either you or I look at with jhat for analysis.  So I can see why the references are anchored in memory.

Andy

On 16/04/2008, jeanlouis.pasturel@xxxxxxxxxxxxxxxxxx <jeanlouis.pasturel@xxxxxxxxxxxxxxxxxx> wrote:

Context :

- JVM IBM 1.5.0 AIX 64 bits

- LTW weaving classes in packages ( WebMethod IS server). The application is big

 

I got a memory leak, with a lot of aspectj classes in the heapdump.

Examples :

-          590 000 instances of org.aspectj.ReferenceType

-          430 000 instances of org.aspectj.UnresolvedType

-          418 000 instances of org.aspectj.ResolvedType

-          280 000 instances of org.aspectj. ResolvedMemberImpl

 

AspectJ Development build of 22032008 (but I am not sure).

 

In aop.xml, in the weaver element,  I have *not* exclude AspectJ package ( org.aspectj..) and I have *not* exclude my own aspect

In the heapdump my aspect is shown once ( default persingleton scope)

The number of classes woven is less than 50.

 

Do you think is a bug?

 

Cordialement / Best regards

 

Jean-Louis Pasturel
jeanlouis.pasturel@xxxxxxxxxxxxxxxxxx

 

 

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************


_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users

 

*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************

Back to the top