Fatal error nullptr check in AsyncModuleExecutionFulfilled

[xrchz]

Version

v22.2.0

Platform

Linux mia 6.9.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 26 May 2024 01:30:29 +0000 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

I have not yet been able to reproduce this except by running a large program (https://github.com/xrchz/rockettree)

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

It is a bit flaky

What is the expected behavior? Why is that the expected behavior?

No crash

What do you see instead?

#
# Fatal error in , line 0
# Check failed: (location_) != nullptr.
#
#
#
#FailureMessage Object: 0x78749e5fa4b0
----- Native stack trace -----



#
# Fatal error in , line 0
# Check failed: (location_) != nullptr.
#
#
#
#FailureMessage Object: 0x78749dffa4b0
----- Native stack trace -----



#
# Fatal error in , line 0
# Check failed: (location_) != nullptr.
#
#
#
#FailureMessage Object: 0x78749d9fa4b0
----- Native stack trace -----



#
# Fatal error in , line 0
# Check failed: (location_) != nullptr.
#
#
#
#FailureMessage Object: 0x78749d3fa4b0
----- Native stack trace -----

 1: 0x5c44f300ba27  [node]
 2: 0x5c44f40a3adf V8_Fatal(char const*, ...) [node]
 1: 0x5c44f300ba27  [node]
 1: 0x5c44f300ba27  [node]
22:56:59: 3460 epochs left to process attestations
 1: 0x5c44f300ba27  [node]
 2: 0x5c44f40a3adf V8_Fatal(char const*, ...) [node]
22:56:59: 3450 epochs left to process attestations
 2: 0x5c44f40a3adf V8_Fatal(char const*, ...) [node]
 2: 0x5c44f40a3adf V8_Fatal(char const*, ...) [node]
22:56:59: 3440 epochs left to process attestations
 3: 0x5c44f3709c04 v8::internal::SourceTextModule::AsyncModuleExecutionFulfilled(v8::internal::Isolate*, v8::internal::Handle<v8::internal::SourceTextModule>) [node]
 4: 0x5c44f3253815 v8::internal::Builtin_CallAsyncModuleFulfilled(int, unsigned long*, v8::internal::Isolate*) [node]
22:56:59: 3430 epochs left to process attestations
 5: 0x5c44f3ec24b6  [node]
fish: Job 1, 'node --trace-exit --node-memory…' terminated by signal SIGTRAP (Trace or breakpoint trap)

Additional information

The lines starting 22:56:59: above are part of my program's output.

[xrchz]

I'm reporting here since I am a bit at a loss how to debug this - pointers appreciated.