Version
v25.9.0
Platform
Linux vm 6.12.73+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.73-1 (2026-02-17) x86_64 GNU/Linux;
Linux vm 6.12.63+deb13-arm64 #1 SMP Debian 6.12.63-1 (2025-12-30) aarch64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
Crashes in some tests from test262:
test/language/statements/using/syntax/using-invalid-arraybindingpattern-after-bindingidentifier.js
test/language/statements/using/syntax/using-invalid-objectbindingpattern-after-bindingidentifier.js
test/language/statements/await-using/syntax/await-using-invalid-arraybindingpattern-after-bindingidentifier.js
test/language/statements/await-using/syntax/await-using-invalid-objectbindingpattern-after-bindingidentifier.js
Reproducible without any special flags. Taking the first one as example:
$ node -e '{using x=null, {}=null;}'
# node[334]: std::string node::GetErrorSource(Isolate *, Local<Context>, Local<Message>, bool *) at ../src/node_errors.cc:154
# Assertion failed: (end) >= (start)
----- Native stack trace -----
1: 0x90ace8 node::Assert(node::AssertionInfo const&) [node]
2: 0x90abf1 [node]
3: 0x90ae92 node::AppendExceptionLine(node::Environment*, v8::Local<v8::Value>, v8::Local<v8::Message>, node::ErrorHandlingMode) [node]
4: 0x90e43c node::errors::DecorateErrorStack(node::Environment*, v8::Local<v8::Value>, v8::Local<v8::Message>) [node]
5: 0x8f2e54 node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [node]
6: 0xbecf61 [node]
7: 0xbeca9d [node]
8: 0xbec3f7 [node]
9: 0x70275363adf6
----- JavaScript stack trace -----
1: makeContextifyScript (node:internal/vm:194:14)
2: compileScript (node:internal/process/execution:420:10)
3: evalTypeScript (node:internal/process/execution:292:22)
4: node:internal/main/eval_string:71:3
Aborted
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
Should throw a SyntaxError, never crash.
What do you see instead?
SIGABRT
Additional information
No response
Version
v25.9.0
Platform
Subsystem
No response
What steps will reproduce the bug?
Crashes in some tests from test262:
Reproducible without any special flags. Taking the first one as example:
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
Should throw a SyntaxError, never crash.
What do you see instead?
SIGABRT
Additional information
No response