How to debug core dump errors?

[jcubic]

I have a Scheme interpreter written in JavaScript and when running a recursive macro I got this error:

<--- Last few GCs --->

[791847:0x6134dd0]      889 ms: Scavenge 21.2 (30.9) -> 13.5 (30.9) MB, 1.09 / 0.00 ms  (average mu = 1.000, current mu = 1.000) allocation failure; 
[791847:0x6134dd0]      898 ms: Scavenge 21.3 (30.9) -> 13.6 (30.9) MB, 1.05 / 0.00 ms  (average mu = 1.000, current mu = 1.000) allocation failure; 
[791847:0x6134dd0]      909 ms: Scavenge 21.4 (30.9) -> 13.7 (46.9) MB, 2.20 / 0.00 ms  (average mu = 1.000, current mu = 1.000) allocation failure; 


<--- JS stacktrace --->

FATAL ERROR: RegExpCompiler Allocation failed - process out of memory
 1: 0xc9e850 node::Abort() [node]
 2: 0xb720ff  [node]
 3: 0xec1a70 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 4: 0xec1d57 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 5: 0x14bfea8  [node]
 6: 0x14b89d8 v8::internal::RegExpDisjunction::ToNode(v8::internal::RegExpCompiler*, v8::internal::RegExpNode*) [node]
 7: 0x14ac3d8 v8::internal::RegExpCapture::ToNode(v8::internal::RegExpCompiler*, v8::internal::RegExpNode*) [node]
 8: 0x14ac449 v8::internal::RegExpCapture::ToNode(v8::internal::RegExpTree*, int, v8::internal::RegExpCompiler*, v8::internal::RegExpNode*) [node]
 9: 0x14c1c0d v8::internal::RegExpCompiler::PreprocessRegExp(v8::internal::RegExpCompileData*, v8::base::Flags<v8::internal::RegExpFlag, int>, bool) [node]
10: 0x14e5c1f v8::internal::RegExpImpl::Compile(v8::internal::Isolate*, v8::internal::Zone*, v8::internal::RegExpCompileData*, v8::base::Flags<v8::internal::RegExpFlag, int>, v8::internal::Handle<v8::internal::String>, v8::internal::Handle<v8::internal::String>, bool, unsigned int&) [node]
11: 0x14e6526 v8::internal::RegExpImpl::CompileIrregexp(v8::internal::Isolate*, v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>, bool) [node]
12: 0x14e70e7 v8::internal::RegExpImpl::IrregexpPrepare(v8::internal::Isolate*, v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>) [node]
13: 0x14e7220 v8::internal::RegExpImpl::IrregexpExec(v8::internal::Isolate*, v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>, int, v8::internal::Handle<v8::internal::RegExpMatchInfo>, v8::internal::RegExp::ExecQuirks) [node]
14: 0x150e27d v8::internal::Runtime_RegExpExec(int, unsigned long*, v8::internal::Isolate*) [node]
15: 0x1934ef6  [node]
Aborted (core dumped)

I'm low on memory, I have 16GB of RAM but right now only 1,8G Free.

Is there something I can do to the code or the RAM is the limitation?

[aduh95]

Looking at the stack trace, it says the out of memory error happens when initializring a RegExp, maybe you could look into optimizing those – I haven't looked at your code, maybe there's a way to achieve what you code is doing using fewer and/or less heavy regexes.

You can also have a look at https://nodejs.org/api/cli.html#useful-v8-options, you can force V8 to spend more work on garbage collector, which might let you avoid the out of memory error.

[jcubic]

Thanks. I solved the issue by switching to Bun which gives a proper stack overflow error.

[jcubic]

Also, regex was not heavy only you increased the number of stack frames so much that there is not enough memory to handle all the available frames.