illegal access FATAL ERROR

[Diogny]

• Version: v12.18.3
• Platform: Windows 10 64-bits
• Subsystem: VS Code

What steps will reproduce the bug?

It happens when debug finished with no errors, but I stopped on breakpoints to inspect variables, click on Stack trace to see where a value is coming from, etc. When ran no stop, or hit Continue on every breakpoint, it's fine, most of the time.

How often does it reproduce? Is there a required condition?

Almost always when I inspect variables on breakpoint

What is the expected behavior?

not debugger error output

What do you see instead?

Additional information

Below is the debugger output:

Debugger listening on ws://127.0.0.1:23199/91d234be-bc21-4519-89c4-a0dd6e724d13
For help, see: https://nodejs.org/en/docs/inspector
undefined:0

illegal access
FATAL ERROR:
node::inspector::Agent::ToggleAsyncHook Cannot toggle Inspector's AsyncHook, please report this.
1: 00007FF793D05EBF napi_wrap+114095
2: 00007FF793CB0B46 v8::base::CPU::has_sse+66998
3: 00007FF793CB1946 v8::base::CPU::has_sse+70582
4: 00007FF793CB1129 v8::base::CPU::has_sse+68505
5: 00007FF793BC38F9 std::basic_ostream<char,std::char_traits >::basic_ostream<char,std::char_traits >+79593
6: 00007FF793FA5E17 v8::internal::compiler::TopLevelLiveRange::has_preassigned_slot+79495
7: 00007FF793F989BD v8::internal::compiler::TopLevelLiveRange::has_preassigned_slot+25133
8: 00007FF793F88668 v8_inspector::V8StackTraceId::V8StackTraceId+46600
9: 00007FF793F88864 v8_inspector::V8StackTraceId::V8StackTraceId+47108
10: 00007FF793BC194D std::basic_ostream<char,std::char_traits >::basic_ostream<char,std::char_traits >+71485
11: 00007FF793BC48E4 std::basic_ostream<char,std::char_traits >::basic_ostream<char,std::char_traits >+83668
12: 00007FF793BC0887 std::basic_ostream<char,std::char_traits >::basic_ostream<char,std::char_traits >+67191
13: 00007FF793BC1BA9 std::basic_ostream<char,std::char_traits >::basic_ostream<char,std::char_traits >+72089
14: 00007FF793BC1FC4 std::basic_ostream<char,std::char_traits >::basic_ostream<char,std::char_traits >+73140
15: 00007FF793BAD480 std::basic_ostream<char,std::char_traits >::put+3552
16: 00007FF793BAE8D3 std::basic_ostream<char,std::char_traits >::put+8755
17: 00007FF793BADDFA std::basic_ostream<char,std::char_traits >::put+5978
18: 00007FF793BAE979 std::basic_ostream<char,std::char_traits >::put+8921
19: 00007FF793C4861F std::basic_ostream<char,std::char_traits >::operator<<+72191
20: 00007FF793C47674 std::basic_ostream<char,std::char_traits >::operator<<+68180
21: 00007FF793D5677B uv_async_send+331
22: 00007FF793D55F1C uv_loop_init+1212
23: 00007FF793D560E4 uv_run+244
24: 00007FF793CF4090 napi_wrap+40832
25: 00007FF793D04B47 napi_wrap+109111
26: 00007FF793C67052 v8::internal::Scope::locals+32082
27: 00007FF793CDA593 node::Start+275
28: 00007FF793B46A9C RC4_options+340380
29: 00007FF7949D34A8 v8::internal::SetupIsolateDelegate::SetupHeap+1300536
30: 00007FFF6CB36FD4 BaseThreadInitThunk+20
31: 00007FFF6E41CEC1 RtlUserThreadStart+33
Process exited with code 134

[bnoordhuis]

Duplicate of #27261. A fix has been merged but not released yet. ETA: Somewhere in the next two or three weeks.