You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2008/12/10 00:14:44 UTC

[jira] Created: (GERONIMO-4456) ClassLoader memory leak caused by AspectJ

ClassLoader memory leak caused by AspectJ
-----------------------------------------

                 Key: GERONIMO-4456
                 URL: https://issues.apache.org/jira/browse/GERONIMO-4456
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
    Affects Versions: 2.2
            Reporter: Kevan Miller
            Assignee: Kevan Miller
             Fix For: 2.2


AspectJ is causing a ClassLoader memory leak. The problem is causing OOME PermGen failures in TCK tests.

The access patterns that keep the classloaders alive are as follows:

{noformat}
org.apache.geronimo.kernel.config.MultiParentClassLoader
  loader of  org.aspectj.weaver.loadtime.DefaultWeavingContext
    weavingContext of  org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor
      weavingAdaptor of  org.aspectj.weaver.loadtime.Aj$ExplicitlyInitializedClassLoaderWeavingAdaptor
	value of  java.util.WeakHashMap$Entry
	  [413] of  java.util.WeakHashMap$Entry[1024]
	    table of  java.util.WeakHashMap
	      weavingAdaptors of  org.aspectj.weaver.loadtime.Aj$WeaverContainer
		[11] of  java.lang.Object[1280]
		  elementData of  java.util.Vector
		    classes of  org.apache.geronimo.kernel.config.MultiParentClassLoader
		      classLoader of  org.apache.geronimo.gbean.runtime.GBeanInstance
			[1283] of  java.lang.Object[2048]
			  table of  java.util.IdentityHashMap
			    instanceRegistry of  org.apache.geronimo.kernel.basic.BasicRegistry
			      instanceRegistry of  org.apache.geronimo.gbean.runtime.GBeanInstance [Stack Local]
{noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (GERONIMO-4456) ClassLoader memory leak caused by AspectJ

Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevan Miller closed GERONIMO-4456.
----------------------------------

    Resolution: Fixed

Upgrade to AspectJ 1.6.2

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=210470 for info about the AspectJ bug.

> ClassLoader memory leak caused by AspectJ
> -----------------------------------------
>
>                 Key: GERONIMO-4456
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4456
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.2
>            Reporter: Kevan Miller
>            Assignee: Kevan Miller
>             Fix For: 2.2
>
>
> AspectJ is causing a ClassLoader memory leak. The problem is causing OOME PermGen failures in TCK tests.
> The access patterns that keep the classloaders alive are as follows:
> {noformat}
> org.apache.geronimo.kernel.config.MultiParentClassLoader
>   loader of  org.aspectj.weaver.loadtime.DefaultWeavingContext
>     weavingContext of  org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor
>       weavingAdaptor of  org.aspectj.weaver.loadtime.Aj$ExplicitlyInitializedClassLoaderWeavingAdaptor
> 	value of  java.util.WeakHashMap$Entry
> 	  [413] of  java.util.WeakHashMap$Entry[1024]
> 	    table of  java.util.WeakHashMap
> 	      weavingAdaptors of  org.aspectj.weaver.loadtime.Aj$WeaverContainer
> 		[11] of  java.lang.Object[1280]
> 		  elementData of  java.util.Vector
> 		    classes of  org.apache.geronimo.kernel.config.MultiParentClassLoader
> 		      classLoader of  org.apache.geronimo.gbean.runtime.GBeanInstance
> 			[1283] of  java.lang.Object[2048]
> 			  table of  java.util.IdentityHashMap
> 			    instanceRegistry of  org.apache.geronimo.kernel.basic.BasicRegistry
> 			      instanceRegistry of  org.apache.geronimo.gbean.runtime.GBeanInstance [Stack Local]
> {noformat}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.