GC overhead limit exceeded, when running tests for Scala plugin


Hi,

I'm trying to run the tests for Scala plugin project in IntelliJ (IDEA X EAP IU98-311, Scala plugin, 0.4.207, Java 1.6.0_22 on Ubuntu 10.04).
Mid way through the 2000+ tests, around FunctionTypeTest, I starts getting these errors and the tests run hangs:

java.lang.OutOfMemoryError: GC overhead limit exceeded
 at org.jetbrains.plugins.scala.lang.psi.stubs.elements.signatures.ScParamElementType.deserializeImpl(ScParamElementType.scala:53)
 at org.jetbrains.plugins.scala.lang.psi.stubs.elements.signatures.ScParamElementType.deserializeImpl(ScParamElementType.scala:19)
 at org.jetbrains.plugins.scala.lang.psi.stubs.elements.wrappers.IStubElementTypeWrapper.deserialize(IStubElementTypeWrapper.java:30)
 at com.intellij.psi.stubs.SerializationManagerImpl.deserialize(SerializationManagerImpl.java:203)
 at com.intellij.psi.stubs.SerializationManagerImpl.deserialize(SerializationManagerImpl.java:206)
 at com.intellij.psi.stubs.SerializationManagerImpl.deserialize(SerializationManagerImpl.java:206)
 at com.intellij.psi.stubs.SerializationManagerImpl.deserialize(SerializationManagerImpl.java:206)
 at com.intellij.psi.stubs.SerializationManagerImpl.deserialize(SerializationManagerImpl.java:206)
 at com.intellij.psi.stubs.SerializationManagerImpl.deserialize(SerializationManagerImpl.java:206)
 at com.intellij.psi.stubs.SerializationManagerImpl.deserialize(SerializationManagerImpl.java:206)
 at com.intellij.psi.stubs.SerializationManagerImpl.deserialize(SerializationManagerImpl.java:206)
 at com.intellij.psi.stubs.SerializationManagerImpl.deserialize(SerializationManagerImpl.java:206)
 at com.intellij.psi.stubs.SerializationManagerImpl.deserialize(SerializationManagerImpl.java:188)
 at com.intellij.psi.stubs.SerializedStubTree.getStub(SerializedStubTree.java:33)
 at com.intellij.psi.stubs.StubTree.readFromVFile(StubTree.java:138)
 at com.intellij.psi.stubs.StubTree.readOrBuild(StubTree.java:102)
 at com.intellij.psi.impl.source.PsiFileImpl.getStubTree(PsiFileImpl.java:599)
 at com.intellij.psi.stubs.StubIndexImpl$1.perform(StubIndexImpl.java:188)
 at com.intellij.psi.stubs.StubIndexImpl$1.perform(StubIndexImpl.java:176)
 at com.intellij.util.indexing.ValueContainer.forEach(ValueContainer.java:56)
 at com.intellij.psi.stubs.StubIndexImpl.get(StubIndexImpl.java:176)
 at org.jetbrains.plugins.scala.caches.ScalaShortNamesCache.getClassNames(ScalaShortNamesCache.java:112)
 at org.jetbrains.plugins.scala.finder.ScalaClassFinder.getClassNames(ScalaClassFinder.scala:25)
 at com.intellij.psi.impl.JavaPsiFacadeImpl.getClassNames(JavaPsiFacadeImpl.java:318)
 at com.intellij.psi.impl.file.PsiPackageImpl.c(PsiPackageImpl.java:419)
 at com.intellij.psi.impl.file.PsiPackageImpl.containsClassNamed(PsiPackageImpl.java:436)
 at com.intellij.psi.impl.file.PsiPackageImpl.processDeclarations(PsiPackageImpl.java:467)
 at org.jetbrains.plugins.scala.lang.psi.impl.ScPackageImpl.processDeclarations(ScPackageImpl.scala:25)
 at org.jetbrains.plugins.scala.lang.resolve.ResolvableStableCodeReferenceElement$class.processQualifierResolveResult(ResolvableStableCodeReferenceElement.scala:56)
 at org.jetbrains.plugins.scala.lang.psi.impl.base.ScStableCodeReferenceElementImpl.processQualifierResolveResult(ScStableCodeReferenceElementImpl.scala:29)
 at org.jetbrains.plugins.scala.lang.resolve.ResolvableStableCodeReferenceElement$class.doResolve(ResolvableStableCodeReferenceElement.scala:85)
 at org.jetbrains.plugins.scala.lang.psi.impl.base.ScStableCodeReferenceElementImpl.doResolve(ScStableCodeReferenceElementImpl.scala:29)



The tests are run with the project's preset jvm args:
-Xms512m -Xmx1024m -XX:MaxPermSize=250m

Any ideas ?
Chi Lang
2 comments
Comment actions Permalink

I have same problems, I don't know now what cause this, but of course this will be fixed. There is no such problem on our buildserver (It seems, something changed in test runner between IDEA EAPs).

Best regards,
Alexander Podkhalyuzin.

0
Comment actions Permalink

We're running into a similar issue that may be related, but the OOM error occurs while compiling the project and using YourKit profiler it seems to be related to the specs.  It is unclear though if this is strictly related to Specs2 or our spec class topology or the structuring of our mocks.  I can provide some memory snapshots if that would help.  This is not on an EAP though, just a 2017.2.6 build.

0

Please sign in to leave a comment.