Crash while load testing a NextJS application

[dmeijboom]

How can we reproduce the crash?

I was testing high memory usage with NodeJS/bun using --inspect in one of our NextJS applications. Unfortunately, I cannot reproduce the issue nor provide a minimal reproduction. But since it crashed (seemingly) randomly with a segfault I didn't want to throw away the report.

Some details:

• We were using NextJS v14.2.6 (standalone build, App Router)
• The route in question (homepage) was using searchParams which means that it wasn't cached
• Testing happened via wrk with the following arguments: wrk -t 4 -c 50 -d 30s --latency http://localhost:3000

Relevant log output

No response

Stack Trace (bun.report)

Bun v1.1.27 (267afa2) on macos aarch64 [AutoCommand]

Segmentation fault at address 0x344000000000000

• 2 unknown/js code
• JSC::RecordedStatuses::finalize
• JSC::CodeBlock::finalizeUnconditionally
• void JSC::IsoCellSet::forEachMarkedCell<void JSC::Heap::finalizeMarkedUnconditionalFinalizers<JSC::CodeBlock, JSC::IsoCellSet>(...)::'lambda'(...)>
• JSC::Heap::finalizeUnconditionalFinalizers
• JSC::Heap::runEndPhase
• JSC::Heap::runCurrentPhase
• WTF::ScopedLambdaFunctor<void (...), JSC::Heap::collectInMutatorThread()::$_0>::implFunction
• JSC::callWithCurrentThreadState

[Jarred-Sumner]

Interesting