Open
Description
How can we reproduce the crash?
I guess having the performance profiler be recording while running (even a small) autocannon benchmark
Relevant log output
auth apis at http://localhost:3001/
web pages being served at http://localhost:3000/
admin apis running at http://localhost:3002/
Connected to Redis
Connected to MongoDB
============================================================
Bun v1.1.20 (ae194892) Linux x64
Linux Kernel v6.9.3 | glibc v2.35
CPU: sse42 popcnt avx avx2
Args: "bun" "--inspect" "src/main.js"
Features: jsc Bun.stderr abort_signal(86) dotenv(2) http_server(4) tsconfig(8)
Builtins: "bun:main" "detect-libc" "node:assert" "node:async_hooks" "node:buffer" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:net" "node:os" "node:path" "node:querystring" "node:stream" "node:string_decoder" "node:timers" "node:tls" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" "node:worker_threads"
Elapsed: 62784ms | User: 75728ms | Sys: 4348ms
RSS: 1.03GB | Peak: 0.50GB | Commit: 1.03GB | Faults: 0
panic: Floating point error at address 0x62C11356E68CStack Trace (bun.report)
Bun v1.1.20 (ae19489) on linux x86_64 [AutoCommand]
Floating point exception at address 0x62C11356E68C
??ld-temp.o:0:JSC::JSRopeString::RopeBuilder<WTF::RecordOverflow>::expandld-temp.o:0:JSC::SlotVisitor::didReachTerminationld-temp.o:0:JSC::SlotVisitor::performIncrementOfDraining(...)::$_2::operator()ld-temp.o:0:JSC::SpaceTimeMutatorScheduler::timeToStopld-temp.o:0:JSC::Heap::resumeThePeripheryld-temp.o:0:WTF::Detail::CallableWrapper<WTF::AutomaticThread::start(...)::$_0, void>::~CallableWrapperld-temp.o:0:JSC::HeapCell::isLiveld-temp.o:0:WTF::Thread::destructTLS??
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
An issue that could cause a crashAn issue that could cause a crashAn issue that occurs on LinuxAn issue that occurs on Linux