Please avoid duplicates

• I checked all open bugs and none of them matched my problem.

Reproducible test case

https://runkit.com/johnp-gh/nock-nock-2771

Nock Version

14.0.0-beta.9

Node Version

22.6.0

TypeScript Version

No response

What happened?

The Nock internal setTimeout/setInterval/setImmediate spies leak memory, as shown in the reproducer and seen in webdriverio/webdriverio#13219 (comment). I don't think that Nock really intends to hold on to already finished, or cleared, timers.

This same issue has previously already reported here, but those tickets were later closed:

• there may be a memory leak because of timers #2428
• The request params was retained in memory after request complete #2436

Would you be interested in contributing a fix?

• yes