3 ms·
Just thought that the `This rework addressed a series of long-standing memory leaks and use-after-free issues in the following APIs that support` part will fina
by derN3rd 3y ago
Just thought that the `This rework addressed a series of long-standing memory leaks and use-after-free issues in the following APIs that support` part will finally solve memory issues with jest, but Simen Bekkhus already posted that it's still an issue... (https://github.com/nodejs/node/issues/35375#issuecomment-1740747711 https://github.com/nodejs/node/issues/35375#issuecomment-174...)
- jmull 3y agoThat's linking to a performance issue, but the nodejs fixes were about memory leaks and use-after-free. So it sounds like different issues.
- inglor 3y agoThere is already a PR on the way to fix the performance regression with what Jest s doing https://github.com/nodejs/node/pull/49950 https://github.com/nodejs/node/pull/49950 Note we also ship a test runner ourselves pretty recently and it may suit your needs.