java.lang.OutOfMemoryError: Java heap space running against Kotlin project
See original GitHub issueHello! I tried to run pitest against a Kotlin project, and it worked great for a small module. I tried on a larger one, and encountered the following error.
VM : OpenJDK 64-Bit Server VM
Vendor : Oracle Corporation
Version : 14.0.1+7
Uptime : 334777
Input ->
1 : -Dfile.encoding=UTF-8
2 : -Duser.country=CA
3 : -Duser.language=en
4 : -Duser.variant
BootClassPathSupported : false
java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: Java heap space
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
at org.pitest.util.CommunicationThread.waitToFinish(CommunicationThread.java:59)
at org.pitest.coverage.execute.CoverageProcess.waitToDie(CoverageProcess.java:35)
at org.pitest.coverage.execute.DefaultCoverageGenerator.gatherCoverageData(DefaultCoverageGenerator.java:138)
at org.pitest.coverage.execute.DefaultCoverageGenerator.calculateCoverage(DefaultCoverageGenerator.java:89)
at org.pitest.coverage.execute.DefaultCoverageGenerator.calculateCoverage(DefaultCoverageGenerator.java:51)
at org.pitest.mutationtest.tooling.MutationCoverage.runReport(MutationCoverage.java:115)
at org.pitest.mutationtest.tooling.EntryPoint.execute(EntryPoint.java:121)
at org.pitest.mutationtest.tooling.EntryPoint.execute(EntryPoint.java:51)
at org.pitest.mutationtest.commandline.MutationCoverageReport.runReport(MutationCoverageReport.java:87)
at org.pitest.mutationtest.commandline.MutationCoverageReport.main(MutationCoverageReport.java:45)
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.base/java.util.TreeMap.put(TreeMap.java:575)
at java.base/java.util.TreeSet.add(TreeSet.java:255)
at org.pitest.coverage.CoverageData.addTestsToBlockMap(CoverageData.java:145)
at org.pitest.coverage.CoverageData.calculateClassCoverage(CoverageData.java:134)
at org.pitest.coverage.execute.DefaultCoverageGenerator$1.accept(DefaultCoverageGenerator.java:184)
at org.pitest.coverage.execute.DefaultCoverageGenerator$1.accept(DefaultCoverageGenerator.java:176)
at org.pitest.coverage.execute.Receive.handleTestEnd(Receive.java:78)
at org.pitest.coverage.execute.Receive.apply(Receive.java:45)
at org.pitest.util.SocketReadingCallable.receiveResults(SocketReadingCallable.java:56)
at org.pitest.util.SocketReadingCallable.call(SocketReadingCallable.java:34)
at org.pitest.util.SocketReadingCallable.call(SocketReadingCallable.java:11)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.lang.Thread.run(Thread.java:832)
1:06:55 p.m. PIT >> SEVERE : Coverage generator Minion exited abnormally due to UNKNOWN_ERROR
Exception in thread "main" org.pitest.util.PitError: Coverage generation minion exited abnormally!
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
[Internal Error] java.lang.OutOfMemoryError: Java heap space ...
Hello! When writing a program with a loop when compilation occurs, this error appears: "Error: Kotlin: [Internal Error] java.lang.
Read more >IntelliJ Idea giving java.lang.OutOfMemoryError - Stack Overflow
I have repeatedly got the java.lang.OutOfMemoryError: Java heap space error when compiling my android project on IntelliJ Idea.
Read more >Gradle Java project: java.lang.OutOfMemoryError - Snyk Support
This is generally caused by a very large Gradle project that does not have sufficient heap space allocated to the project. You can...
Read more >java.lang.OutOfMemoryError: Java heap space - Plumbr
The java.lang.OutOfMemoryError: Java heap space error will be triggered when the application attempts to add more data into the heap space area, ...
Read more >[Solved]-Minify WithR8 throws java.lang.OutOfMemoryError
Coding example for the question Minify WithR8 throws java.lang.OutOfMemoryError: Java heap space-kotlin.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
1.9.0 has now been released. It certainly improves things greatly for assertj. It would be good to know how well it addresses @JGulbronson original problem.
Appologies for leaving this sitting here for so long. A fix should be in the 1.9.0 release.