Boxfort consumes all cpu when left open
Bqleine opened this issue · 3 comments
I had an infinite loop in some of my criterion tests, so I was obliged to kill the processes in order to get going. With time I notice a considerable amount of lag on my pc, turns out boxfort workers had been left open, and were consuming all of the cpu.
The workers should have died along with criterion, by either noticing criterion was gone or maybe criterion passing the signal if that's possible.
That sounds pretty bad. What version are you using, and do you have a way to reproduce this? I'm not noticing any issues on my end.
After doing some quick tests, I was not able to reproduce the issue on a blank project, it seems this only happens when the tests won't exit on SIGTERM (this happened with infinite loops on my bigger project). When the tests are able to close correctly on SIGTERM there's no problem, I'll take a look later in the week to a way to reproduce it.