Closed
Description
Version
v22.5.1
Platform
Debian 5.10.103-1 x86_64
Subsystem
No response
What steps will reproduce the bug?
Hi,
I want to report a node bug, by running the following code snippet, node.js gives a FATAL error.
Object.defineProperty(Object.prototype, '0', {
set() {
console.log(123);
}
});
const http = require('http');
AH
How often does it reproduce? Is there a required condition?
By just running the given code, node runtime gives node crash.
What is the expected behavior? Why is that the expected behavior?
Not a crash, by looking at the stack trace, it seems it is connected to v8::FromJust Maybe value is Nothing
.
What do you see instead?
FATAL ERROR: v8::FromJust Maybe value is Nothing
----- Native stack trace -----
1: 0xe22fb7 node::OnFatalError(char const*, char const*) [node]
2: 0x122ada6 v8::Utils::ReportApiFailure(char const*, char const*) [node]
3: 0x10da3d5 node::TTYWrap::GetWindowSize(v8::FunctionCallbackInfo<v8::Value> const&) [node]
4: 0x7f44475cf6e2
----- JavaScript stack trace -----
1: WriteStream (node:tty:115:28)
2: createWritableStdioStream (node:internal/bootstrap/switches/is_main_thread:56:16)
3: getStdout (node:internal/bootstrap/switches/is_main_thread:153:12)
4: get (node:internal/console/constructor:207:42)
5: value (node:internal/console/constructor:338:50)
6: log (node:internal/console/constructor:385:61)
7: set (/home/abdullah/node-deno-bun/test.js:3:25)
8: WriteStream (node:tty:115:28)
9: createWritableStdioStream (node:internal/bootstrap/switches/is_main_thread:56:16)
10: getStdout (node:internal/bootstrap/switches/is_main_thread:153:12)
Aborted
Additional information
No response