Closed
Description
Version
v18.18.0
Platform
Linux 6.2.0-37-generic #38~22.04.1-Ubuntu SMP
Subsystem
lib
What steps will reproduce the bug?
echo 'console.log("hello")' | node --jitless --frozen-intrinsics
Warning: disabling flag --expose_wasm due to conflicting flags
node:internal/freeze_intrinsics:224
WebAssembly.Module.prototype,
^
TypeError: Cannot read properties of undefined (reading 'Module')
at module.exports (node:internal/freeze_intrinsics:224:17)
at initializeFrozenIntrinsics (node:internal/process/pre_execution:598:42)
at setupUserModules (node:internal/process/pre_execution:132:3)
at prepareExecution (node:internal/process/pre_execution:113:5)
at prepareMainThreadExecution (node:internal/process/pre_execution:40:3)
at node:internal/main/eval_stdin:18:1
Node.js v18.18.0
How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
That --jitless and --frozen-intrinsics are not mutually exclusive.
What do you see instead?
node:internal/freeze_intrinsics:224
WebAssembly.Module.prototype,
^
TypeError: Cannot read properties of undefined (reading 'Module')
at module.exports (node:internal/freeze_intrinsics:224:17)
Additional information
It looks like the problem still exists in the latest node:
https://github.com/nodejs/node/blob/v21.5.0/lib/internal/freeze_intrinsics.js#L223
Metadata
Metadata
Assignees
Labels
No labels