How to debug a crash when building project

[mlilback]

I'm working on a cli vite spa. It works perfectly fine in dev mode. But anytime I try to build it, I get an out of memory error. No matter what size I set max-old-space-size to, it still uses it all up until crash. (I've tried up to 20 GB). I know node has a --verbose option, but I can't find any way to set it when I run quasar build. The stack trace doesn't seem helpful, and neither are any of the stack traces shown for other threads in the MacOS crash log.

How can I track down what the problem is?

Here is the command line input/output:

$ NODE_OPTIONS=--max-old-space-size=20480  quasar build -d

 .d88888b.
d88P" "Y88b
888     888
888     888 888  888  8888b.  .d8888b   8888b.  888d888
888     888 888  888     "88b 88K          "88b 888P"
888 Y8b 888 888  888 .d888888 "Y8888b. .d888888 888
Y88b.Y8b88P Y88b 888 888  888      X88 888  888 888
 "Y888888"   "Y88888 "Y888888  88888P' "Y888888 888
       Y8b


 Build mode............. spa
 Pkg quasar............. v2.7.5
 Pkg @quasar/app-vite... v1.0.5
 Pkg vite............... v2.9.13
 Debugging.............. enabled
 Publishing............. no

 App • Cleaned build artifact: "/Users/mlilback/working/rc2/rust/notecalc-client/dist/spa"
 App •  WAIT  • Compiling of SPA UI with Vite in progress...

<--- Last few GCs --->

[31819:0x7fe308008000]   252694 ms: Mark-sweep 20071.5 (20521.7) -> 20060.5 (20525.4) MB, 6263.4 / 0.0 ms  (average mu = 0.165, current mu = 0.011) task scavenge might not succeed
[31819:0x7fe308008000]   263668 ms: Mark-sweep 20074.5 (20525.9) -> 20064.5 (20528.9) MB, 10911.2 / 0.0 ms  (average mu = 0.068, current mu = 0.006) task scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
 1: 0x10df3eef5 node::Abort() (.cold.1) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
 2: 0x10cc32869 node::Abort() [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
 3: 0x10cc329df node::OnFatalError(char const*, char const*) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
 4: 0x10cdb4f07 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
 5: 0x10cdb4ea3 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
 6: 0x10cf56585 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
 7: 0x10cf54f0c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
 8: 0x10cfe3e0d v8::internal::ScavengeJob::Task::RunInternal() [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
 9: 0x10cca064b node::PerIsolatePlatformData::RunForegroundTask(std::__1::unique_ptr<v8::Task, std::__1::default_delete<v8::Task> >) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
10: 0x10cc9f0e7 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
11: 0x10d60375b uv__async_io [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
12: 0x10d61754b uv__io_poll [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
13: 0x10d603ce1 uv_run [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
14: 0x10cb63f9f node::SpinEventLoop(node::Environment*) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
15: 0x10cc73f01 node::NodeMainInstance::Run(int*, node::Environment*) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
16: 0x10cc73b59 node::NodeMainInstance::Run(node::EnvSerializeInfo const*) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
17: 0x10cbfe95b node::Start(int, char**) [/Users/mlilback/.nodenv/versions/16.16.0/bin/node]
18: 0x11f90252e 
[1]    31819 abort      NODE_OPTIONS=--max-old-space-size=20480 quasar build -d

[MilosPaunovic]

quasar build --debug

[mlilback]

The -d I'm using is the same as --debug. That just skips some optimizations, it doesn't affect the actual build process.

[mlilback]

Turned out to be some type of dependency issue. I upgraded all dependencies and the problem went away.