Open kazcw opened 3 weeks ago
Hello Kaz, are you sure the OOM
error comes from project-manager
process? Then I remove the compiler label. It would be good to provide some additional information about the crash. The best would be to get heap dump when the OOM error happens.
Are you (can you) build the project-manager
executable yourself? In such case we:
Let's try the JVM variant first:
project-manager
as a JVM ProcessRunning sbt
command:
sbt:enso> project-manager/assembly
generates project-manager.jar
. Running that JAR as:
java -XX:+HeapDumpOnOutOfMemoryError -jar project-manager.jar
and reproducing the OutOfMemoryError
should generate an .hprof
file, print its location on console and only then crash. Having such .hprof
file would allow us to evaluate its content and guess what is actually going wrong in there.
I'm consistently getting a OOM error in the Project Manager process shortly after opening the Selecting and Joining Data example project (various stack traces; the allocation that fails is not consistent at all). The crash occurs with a used heap size of 2GB (25% of the physical memory on the M1 Mac I'm testing on).