Main node process crashes with OOM error about workerpool HOT 3 CLOSED

@VP-0822 maybe you can take one of the simple examples provided with the library, for example dedicatedWorker.js, remove the pool..terminate(), and monitor how that behaves on your machine, and see what memory it uses for process vs thread.

It's hard to tell why the OOM error occurs without actually debugging it. An important difference with worker_threads is that they share memory with the main process, where as a child_process has it's own memory. Suppose both your main process and your worker use 6GB of memory. That will work fine with child_process when you have --max-old-space-size=8192, but will be a problem if you use worker threads since the total memory is 12 GB, above the max of 8GB.

The following node.js issue may be relevant too since I see you're configuring both --max-old-space-size=8192 and "maxOldGenerationSizeMb":768: nodejs/node#43991.

from workerpool.

@josdejong Thanks for the hint. I raised the issue with the library which is throwing this error and they might fix it soon :)

from workerpool.

👍

from workerpool.