You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the test code from https://github.com/laverdet/isolated-vm/blob/main/tests/catastrophic-error.js#L14, I'm testing as to the behaviour of OOM conditions. However, when running the following (e.g. just with node example.mjs), the memorySize limit isn't applied and the node process continues using 100% CPU and consuming memory until manually killed.
By comparison, running the example from https://github.com/laverdet/isolated-vm/?tab=readme-ov-file#examples behaves as the example shows, with the process ending with RangeError. Decreasing the memorySize in the example works - dropping the limit to 8MB sees the script end after 10MB.
Versions
isolated-vm v4.7.2
Node.js v21.6.2
gcc --version:
Apple clang version 15.0.0 (clang-1500.1.0.2.5)
Target: arm64-apple-darwin23.3.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
macOS 14.3.1
The text was updated successfully, but these errors were encountered:
Using the test code from https://github.com/laverdet/isolated-vm/blob/main/tests/catastrophic-error.js#L14, I'm testing as to the behaviour of OOM conditions. However, when running the following (e.g. just with
node example.mjs
), thememorySize
limit isn't applied and thenode
process continues using 100% CPU and consuming memory until manually killed.By comparison, running the example from https://github.com/laverdet/isolated-vm/?tab=readme-ov-file#examples behaves as the example shows, with the process ending with
RangeError
. Decreasing thememorySize
in the example works - dropping the limit to 8MB sees the script end after 10MB.Versions
isolated-vm
v4.7.2gcc --version
:The text was updated successfully, but these errors were encountered: