OutOfMemoryError in ReallySimpleSwingDemoTest #227
Comments
|
From johan.ha...@gmail.com on November 30, 2009 07:25:37 This is a known problem and we're going to work with it on Thursday! Status: Accepted |
|
From rlag...@gmail.com on January 03, 2010 06:37:23 Hi! i have the same problem when running my tests. Is it possible to get any date Thanks |
|
From johan.ha...@gmail.com on January 09, 2010 07:32:12 Unfortunately I don't. We still haven't managed to find out what's causing the memory |
|
From kristof....@gmail.com on May 17, 2010 04:41:36 We are also getting java.lang.OutOfMemory problems when running powermock tests with |
|
From johan.ha...@gmail.com on May 17, 2010 04:53:01 They should indeed! We haven't managed to find out why the MockCL isn't GC:ed though. |
|
From kristof....@gmail.com on May 17, 2010 06:21:19 The problem I was having, was that spring and log4j classes were also loaded by the I wonder why all classes (except the deferred ones) are actually loaded by the |
|
From johan.ha...@gmail.com on May 17, 2010 06:34:34 Good question. To be honest I don't really remember why. We must refactor the |
|
From Alexandr...@gmail.com on June 24, 2010 01:56:39 any progress on this ? :( |
|
From kristof....@gmail.com on June 24, 2010 04:27:37 I think I understand by now why all other classes are loaded by default by the MockClassLoader. I think it's because classes use the ClassLoader by which they are loaded themselves to find other classes they use. That way, you make sure the mocked classes are loaded by the MockClassLoader. By using the PowerMockIgnore annotation, you can tell Powermock: Hey, I'm sure this class is not using my mocked class underneath, so you can load it by the system ClassLoader. At least, that's my interpretation. I'm not 100% sure I'm right on this. |
|
From johan.ha...@gmail.com on July 14, 2010 08:05:13 I've experimented a bit with clearing the ClassPool in the past but I couldn't find a good solution. I think I ended up with ClassNotFoundException's in some subsequent tests when running in a suite. |
|
From deepsh...@gmail.com on July 17, 2010 00:27:37 For me the @PowerMockIgnore fixed the issue for a few days. Later the OutOfMemoryError re-appeared. Surprisingly, this issue only appear for me on a 64 bit JDK, it did not appear on 32 bit JDK. Installed the 32 bit JDK, ran all the tests and bingo! All of them pass. Visit this link for details. http://www.gitshah.com/2010/07/how-to-fix-outofmemoryerror-when_17.html |
|
From johan.ha...@gmail.com on July 22, 2010 02:25:06 Labels: -Milestone-Release1.4 Milestone-Release1.5 |
|
From johan.ha...@gmail.com on July 22, 2010 05:14:17 While I haven't solved the problem there has at least been some progress today. The OutOfMemoryError no longer occurs for me after I've clean up some state in PowerMockRunner (by setting suiteChunker to null in AbstractCommonPowerMockRunner#run method). I'll include this fix in 1.4 and you can try it out if it makes any difference for you. |
|
From jussi.ni...@gmail.com on September 08, 2010 05:51:46 Just made some profiling for this and it seems that mockClassLoader is created for each test and is kept in PermGen. This was with version 1.4.5 (powermock-module-junit4 and powermock-api-mockito). Hope you get this fixed soon! |
|
From marci...@gmail.com on October 25, 2010 13:49:31 This issue happened with me when mocking static final methods using the @PrepareForTest annotation on the METHOD. Maybe works as a workaround for you guys. |
|
From ilinca.v...@gmail.com on November 18, 2010 05:13:08 I'm using powermock 1.4.5, and I still have problems. Moved my @PrepareForTest statement to class instead of method, and while I don't get the same OutOfMemory error, some methods seem to not pick up on the PrepareForTest annotation, meaning I have to declare the same annotation, I have for the class for certain methods anyway, if I want to avoid getting assertion errors. |
|
From johan.ha...@gmail.com on December 27, 2010 01:24:17 We've instigated this a bit further and we think that the problem lies not in PowerMock but in EasyMock (and possibly Mockito but we haven't looked at Mockito yet). I've created a patch for EasyMock to solve one of the two problems that we've found. The issue is here: https://sourceforge.net/tracker/?func=detail&aid=3145906&group_id=82958&atid=567837 |
|
From johan.ha...@gmail.com on December 27, 2010 04:58:23 Just committed code to PowerMock that cleans out some of EasyMocks state after each test method. This seems to reduce memory consumption by 75% (without applying the EasyMock patch mentioned above). |
|
From Alexandr...@gmail.com on December 28, 2010 00:16:39 i have encountered this problem with mockito, so it's there too. |
|
From johan.ha...@gmail.com on December 28, 2010 00:35:51 Yes there's a problem with Mockito as well. I tried to do a similar thing in Mockito as with EasyMock but it doesn't seem to work all that well. I've managed to clean up almost everything but there's one class that prevents the classloader from being GC:ed and that's a PowerMock class called NewInvocationSubstitute. To my understanding the reason for it is that CGLib holds a reference to the classloader. But no matter how much I try I haven't found a way to solve it without failing the tests. |
|
From johan.ha...@gmail.com on December 28, 2010 00:40:13 Still it's better now than it was before. The only time you'll run into trouble now (I think) is when you mock new using (whenNew) because that's when the NewInvocationSubstitute is used. |
|
From johan.ha...@gmail.com on April 10, 2011 05:51:49 Labels: -Milestone-Release1.5 Milestone-Release1.6 |
|
From dmeibu...@gmail.com on September 09, 2011 19:02:22 See also related Issue 346 . |
|
From mike.kol...@gmail.com on September 14, 2011 22:48:23 When will this be fixed for Mockito? |
|
From johan.ha...@gmail.com on September 14, 2011 23:14:09 I fixed several OOM issues related to PowerMock and Mockito a while ago. It takes a tremendous amount of time (at least for me) to track them down and fix them. I don't remember everything so clearly now but I think there was one issue OOM that I failed to resolve last time I checked that had to do with new instance mocking. Is this the issue you're experiencing? |
|
From mike.kol...@gmail.com on September 14, 2011 23:49:08 We are using PowerMock + Mockito to mock out calls to static methods in our tests. We were getting lots of these errors in mvn build output, which we first ignored: log4j:ERROR A "org.apache.log4j.xml.DOMConfigurator" object is not assignable to a "org.apache.log4j.spi.Configurator" variable. After a few more tests were added, the build was starting to fail because of: We tried using @PowerMockIgnore("org.apache.log4j.*"), but that didn't help much. |
|
From mason....@gmail.com on November 09, 2011 23:34:02 I also getting the following error, when using powermock-mockito-junit-1.4.10 suit。 log4j:ERROR A "org.apache.log4j.ConsoleAppender" object is not assignable to a "org.apache.log4j.Appender" variable. |
|
From johan.ha...@gmail.com on November 10, 2011 11:14:57 This has nothing to do with this issue. See FAQ |
|
From vivek.na...@gmail.com on September 27, 2012 14:01:23 Has this issue been solved in the latest release of PowerMock? |
|
From johan.ha...@gmail.com on September 27, 2012 22:24:07 If I remember it correctly there was one memory leak that I couldn't track down but I fixed most of them. I think that's why the issue has not yet been closed. |
|
From michal.r...@gmail.com on January 19, 2013 07:56:17 Are there any updates to this issue ? |
|
From johan.ha...@gmail.com on January 20, 2013 11:08:53 I suppose you're running into OOM issues? |
|
From michal.r...@gmail.com on February 03, 2013 06:23:25 @johan: That's right - OOM. For 21 test classes with PowerMock runner, I have 21 different class definiotions... |
|
From johan.ha...@gmail.com on February 03, 2013 08:56:24 Do you have any experience with tracking down OOM issues? In that case it'll be a huge help if you can try to find out what's happening. I remember I dug into some issues a couple of years ago and for me it took 2 days or so of my holiday to track things down and fix them (fixing was the easy part though). I don't see myself having the time to do something similar now in a foreseeable future :( |
|
From hen...@akarlsson.com on June 26, 2013 05:39:33 Johan: Please see https://code.google.com/p/mockito/issues/detail?id=437 for two issues with PermGen OOM from Powermock/Mockito. Maybe they can be solved from Powermock? Might not be the same issue as the original issue here, but at least they will fix some OOM problems. These two problems used about 62% of the memory when I analyzed a thread dump from our JUnit tests. |
|
From johan.ha...@gmail.com on June 26, 2013 05:44:09 Thanks for the pointer! It would be really great if you (or anyone else) could help out tracking this down and perhaps even provide a patch. |
|
From hen...@akarlsson.com on June 27, 2013 03:32:29 I did some investigations regarding this and managed to solve the problem by:
This has solved most of our memory problems. Our test suite is now using almost half the memory it used to. There are however still leaks of javassist.ClassPool, I will see if I find some time to take a look at them as well. Unfortunately I have some Maven problems with the project (I'm not used to Maven..) with failing tests in powermock-module-test-easymock-junit4 (where I have not changed anything), but I have attached the patch with the changes that I have made. Attachment: patch.txt |
|
From hen...@akarlsson.com on June 27, 2013 08:28:08 It seems like the ClassPool leaks are from MockClassLoader "leaks", which in our test suite was due to two of our third party applications was leaving some ThreadLocals and other running threads. This prevented the MockClassLoader to be garbage collected. |
|
From johan.ha...@gmail.com on June 30, 2013 23:06:58 Thanks a lot for helping out Henrik! It's really invaluable! It would have taken me a great amount of time to track this down and fix so I'm really thankful. I've applied the patch to trunk now. Please try it out if you like. |
|
From hen...@akarlsson.com on August 06, 2013 01:35:09 I am now back from my vacation and have successfully tested the trunk version in our project. Thank you Johan for quickly adding the patch! |
|
From deepthi...@gmail.com on November 14, 2013 22:24:56 Hi, I am using powermock version 1.4.10 with jmock/Easymock |
|
From soul...@gmail.com on February 07, 2014 04:48:57 PowerMock 1.5.1 - still OutOfMemory. But if I use 1.5.4 - everything is ok! |
|
From rasmusse...@gmail.com on June 23, 2014 05:46:32 What is the current status? Has this issue been fixed? |
|
I've just run into this same issue running: I'm running a test suite that runs about 500 tests and my PermGen is filled with javaassist.ClassPool objects that take up ~4mb a piece. What is the fix for this issue? Should we be doing something specific in our test setup/tear down? EDIT: |
|
PowerMock uses a new class loader for each test class (or even test when The issue became worse due to that all classes except system and that added to |
From hugo.josefson.old@gmail.com on November 24, 2009 19:44:46
What steps will reproduce the problem? 1. checkout entire subversion repo
2. cd trunk
3. mvn install
What is the expected output?
BUILD SUCCESSFUL
What do you see instead?
Running samples.junit4.swing.ReallySimpleSwingDemoTest
org.apache.maven.surefire.booter.SurefireExecutionException: Java heap
space; nested exception is java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
at javassist.bytecode.CodeAttribute.(CodeAttribute.java:105)
at javassist.bytecode.AttributeInfo.read(AttributeInfo.java:78)
at javassist.bytecode.MethodInfo.read(MethodInfo.java:498)
at javassist.bytecode.MethodInfo.(MethodInfo.java:79)
at javassist.bytecode.ClassFile.read(ClassFile.java:716)
at javassist.bytecode.ClassFile.(ClassFile.java:85)
at javassist.CtClassType.getClassFile2(CtClassType.java:190)
at javassist.CtClassType.makeFieldCache(CtClassType.java:760)
at javassist.CtClassType.getMembers(CtClassType.java:751)
at javassist.CtClassType.getMethod0(CtClassType.java:1049)
at javassist.CtClassType.getMethod(CtClassType.java:1038)
at javassist.expr.MethodCall.getMethod(MethodCall.java:114)
at
org.powermock.core.transformers.impl.MainMockTransformer$PowerMockExpressionEditor.edit(MainMockTransformer.java:237)
at javassist.expr.ExprEditor.loopBody(ExprEditor.java:191)
at javassist.expr.ExprEditor.doit(ExprEditor.java:90)
at javassist.CtClassType.instrument(CtClassType.java:1289)
at
org.powermock.core.transformers.impl.MainMockTransformer.transform(MainMockTransformer.java:70)
at
org.powermock.core.classloader.MockClassLoader.loadMockClass(MockClassLoader.java:204)
at
org.powermock.core.classloader.MockClassLoader.loadModifiedClass(MockClassLoader.java:146)
at
org.powermock.core.classloader.DeferSupportingClassLoader.loadClass(DeferSupportingClassLoader.java:61)
at java.lang.ClassLoader.loadClass(ClassLoader.java:254)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:399)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:700)
at java.lang.ClassLoader.defineClass(ClassLoader.java:545)
at
org.powermock.core.classloader.MockClassLoader.loadMockClass(MockClassLoader.java:211)
at
org.powermock.core.classloader.MockClassLoader.loadModifiedClass(MockClassLoader.java:146)
at
org.powermock.core.classloader.DeferSupportingClassLoader.loadClass(DeferSupportingClassLoader.java:61)
at java.lang.ClassLoader.loadClass(ClassLoader.java:254)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:399)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
Please refer to
/Users/hugo/code/other/powermock/trunk/modules/module-test/powermock/junit4-test/target/surefire-reports
for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 19 seconds
[INFO] Finished at: Tue Nov 24 19:37:18 CET 2009
[INFO] Final Memory: 42M/94M
[INFO] ------------------------------------------------------------------------
Additional information:
[550:trunk]$ echo $MAVEN_OPTS
-Xmx3072m -XX:MaxPermSize=768m
Original issue: http://code.google.com/p/powermock/issues/detail?id=207
The text was updated successfully, but these errors were encountered: