Studio crash during process execution

varunm1

Hello,

When I am trying to run a process in RM studio, I am encountering the error in the below screenshot after 30 minutes (approx) of process execution. I attached the studio log in this thread. Is this some kind of memory issue?



@Marco_Boeck

Marco_Boeck

Hi,

Thanks for sending the file!
The thread that crashed in the JVM was indeed GCTaskThread, which indicates that the garbage collection exploded while trying to free memory.
Unfortunately, that knowledge does not really help much, as there is nothing we can really jump on to fix..
When Java runs out of memory, a lot of weird things can happen, from a frozen state, over a well-defined "you're out of memory" error which we catch in Studio to display it, to a complete JVM crash (with varying reasons within the err log file). And potentially even more.

The exact behavior depends on many outside factors, like OS, Java version, hardware, drivers, OS load, etc etc.
I'm afraid there is nothing I can do to help you

Regards,
Marco

Marco_Boeck

Hi,

Potentially, at least it's a devestating crash of the JVM. If you can, it would be very helpful if you could start Studio via the .bat file, which opens the CMD window which maybe can also contain the JVM crash error.

Regards,
Marco

varunm1

Thanks @Marco_Boeck I will launch using a batch file and inform you if the issue repeats.

varunm1

Hello @Marco_Boeck

Here is the error displayed in cmd.

Marco_Boeck

Hi,

Java JVM crashes we cannot do anything about I'm afraid. Though I still would be intersted in the contents of the hs_err_pid13044.log file. (PM if you'd like).
They often happen in low memory situations, where for one reason or another the JVM crashes while trying to get more memory.

Regards,
Marco

varunm1

Thanks @Marco_Boeck. I am running multiple algorithms in a process and this error is specific to the random forest algorithm as others worked fine. I will reduce the hyperparameter search space and data and try to mitigate this. 

I suspected it might be out of memory, but RM used to inform if there is a memory issue as mentioned by you, so I wanted to double-check. 

Again, thanks for taking a look at this and informing the reason.