James Murdza

I've had a deeper look at the code, and I think I get the source of confusion: The start and wait methods are completely separate, meaning they each have their...

Maybe something like: ``` let procWithCustomHandler = sandbox.process.start({ timeout: 60000 }); procWithCustomHandler.wait({ timeout: 300000 }) ``` and ``` sandbox.process.startAndWait({ startTimeout: 60000, waitTimeout: 300000 }); ``` or ``` sandbox.process.startAndWait({ timeout: 60000...

@JM-delatorre Thanks for your comment, that helped me. I added `"use client"` to the top of the file and it worked.

Interesting, I will try this. Any explanation why this would work?

@Fhwang0926 Were you able to figure out any solution?

Hi @syscl , I am encountering the exact same crash/memory leak as the original poster. I tried deleting all of the code for non-turboboost features, (lines 175-234 in CPUTune.cpp) but...

When I comment out everything in readConfigAtRuntime the leak does not happen. This is in the latest version (2.2.5). I recently upgraded from 1.9.0 to 2.2.1 which is when I...

> Thanks @jamesmurdza! Which old version also has the leak you've mentioned? Hi @syscl — That's what I would like to know as well! I will do some tests and...

Hi @syscl, the problem seems to be related to the timer. This new code causes a memory leak: ``` if (timerSource && !this->isInactive()) { // Don't use sender here which...

> @syscl the difference between sender->setTimeoutMS(updateInterval); and timerSource->setTimeout(updateInterval). is `MS` :3 It should be `timerSource->setTimeoutMS(updateInterval)` @sooxt98 Good catch. It looks like setTimeout() defaults to nanoseconds instead of milliseconds. Default UpdateInterval...