We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I want to report a bug causing a segmentation fault in Bun, it can reproduced by running the following code example:
function Module() { (async function () { const output = await (Bun.$)`pwd`.text(); console.log(output); })(); new Float64Array(badObj); } function f() { try { var fuse = f(); if (fuse == 0) Module(); } catch (e) { return 0; } } f();
Regards,
AH
Bun Canary v1.1.39-canary.38 (00b7d647) macOS x64 macOS v15.3.1 CPU: sse42 popcnt avx avx2 Args: "bun" "run" "bug.js" Features: jsc Builtins: "bun:main" Elapsed: 24ms | User: 21ms | Sys: 14ms RSS: 25.76MB | Peak: 25.76MB | Commit: 1.07GB | Faults: 0 panic(main thread): Segmentation fault at address 0x5 oh no: Bun has crashed. This indicates a bug in Bun, not your code. To send a redacted crash report to Bun's team,
Bun v1.1.39-canary (00b7d64) on macos x86_64 [RunCommand]
00b7d64
Segmentation fault at address 0x00000005
??
Features: jsc
Sentry Issue: BUN-22K
The text was updated successfully, but these errors were encountered:
No branches or pull requests
How can we reproduce the crash?
Hi,
I want to report a bug causing a segmentation fault in Bun, it can reproduced by running the following code example:
Regards,
AH
Relevant log output
Stack Trace (bun.report)
Bun v1.1.39-canary (
00b7d64
) on macos x86_64 [RunCommand]Segmentation fault at address 0x00000005
??
??
??
??
??
Features: jsc
Sentry Issue: BUN-22K
The text was updated successfully, but these errors were encountered: