- Version:
master / v12.0.0
- Platform: any
- Subsystem: V8
This is an upstream bug and there's already an issue in the V8 tracker as well as a PR to fix it, but since we're about to release v12.0.0 and the issue will be present there, I think it's a good idea to have this registered here in case users stumble upon that.
The --interpreted-frames-native-stack flag - which is used to allow system profilers to understand V8 interpreted frames - is not compatible with code cache, which we introduced a while back in #24950. If we try to run Node.js with this flag - regardless of the script being executed -, Node.js will crash:
$ ./node --interpreted-frames-native-stack
#
# Fatal error in , line 0
# Check failed: !obj->IsCode().
#
#
#
#FailureMessage Object: 0x7ffc8458e3a0[1] 16377 illegal hardware instruction (core dumped) ./node --interpreted-frames-native-stack
We need to backport https://chromium-review.googlesource.com/c/v8/v8/+/1570582 once it lands upstream, as well as re-enable the Linux perf tests on our V8 CI machines (nodejs/build#1774) once the flag is fixed.
master/ v12.0.0This is an upstream bug and there's already an issue in the V8 tracker as well as a PR to fix it, but since we're about to release v12.0.0 and the issue will be present there, I think it's a good idea to have this registered here in case users stumble upon that.
The
--interpreted-frames-native-stackflag - which is used to allow system profilers to understand V8 interpreted frames - is not compatible with code cache, which we introduced a while back in #24950. If we try to run Node.js with this flag - regardless of the script being executed -, Node.js will crash:We need to backport https://chromium-review.googlesource.com/c/v8/v8/+/1570582 once it lands upstream, as well as re-enable the Linux perf tests on our V8 CI machines (nodejs/build#1774) once the flag is fixed.