Bloop uses all of my CPU and won't stop until I send it SIGKILL

[tmccombs]

I'm not sure what triggers it, several times, I have seen bloop get into a state where it uses up 100% of most of my CPU cores, which leads to my cooling fans going crazy. When this happens, neither closing my editor, not sending SIGTERM to the bloop process seems to do anythilng. Nor does it ever seem to recover on its own. The only way I've found to get out of this state is to send a SIGKILL signal to the process.

[tgodzik]

Thanks for reporting! I haven't seen this happen before. Looks like some kind of an infinite loop in the compiler or GC issues. Would you be able to run jstack (it's found along the java binary) and try to see if it's maxing its heap usage?

[tmccombs]

When I attempt to run jstack against the pid I get:

24914: Unable to open socket file /proc/24914/root/tmp/.java_pid24914: target process 24914 doesn't respond within 10500ms or HotSpot VM not loaded

[tgodzik]

Looks like a GC issue, do you know much memory it has? By default we set 4GB, which should be plenty. Is it a large project? Would increasing it help? You can tinker with the Bloop jvm options and see if there is anything that helps.

[tmccombs]

Yes, it is a large project. I have tried going up to 8GB to fix this, and still encountered it. I've tried going up even higher, we'll see what happens.

[tgodzik]

Yes, it is a large project. I have tried going up to 8GB to fix this, and still encountered it. I've tried going up even higher, we'll see what happens.

We could have some kind of a leak, but I am not sure what that could be. Maybe running jstack before the memory goes too large would show the problem already? Heap dump could also help, but it's almost impossible to work on a too large a heap dump.