Repository navigation
test-wasm-allocation[-memory64] failures with V8 14.6 in worker thread #62870
Description
Activity
- added 2 commits that reference this issue
on Apr 27, 2026 Looked into it a bit and I think this might be a desirable behavior change in 14.6: previously when there's not enough virtual memory to allocate the cage, V8 would throw an allocation error; now, before it throws the allocation error, V8 triggers the near heap limit callback first, which in the case of workers we would report it to the parent and then just let the worker die, because we assume when the heap limit is near the worker is not far from dying; but for wasm allocation failures, this is a bit too pessimistic.
Potentially we can add an option for workers to not die when the heap limit is reached and just emit an event to the parent for cases like this where we don't have to be so pessimistic, and use that in our worker test runner.
This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Refs: #61898
The worker is terminated because it runs out of memory, instead of throwing the expected error.