You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bun build src/main.ts --target=bun --minify--sourcemap--outfile main.js
bun run main.js
Relevant log output
Bun v1.1.17 (bb66bba1) Linux x64
Linux Kernel v6.9.5 | glibc v2.39
Args: "bun""run""main.js"
Features: jsc Bun.stdin(2) bunfig dotenv shell(4) spawn(2) tsconfig
Builtins: "abort-controller""bun:ffi""bun:main""bun:sqlite""node:buffer""node:child_process""node:crypto""node:dns""node:events""node:fs""node:http""node:https""node:os""node:path""node:process""node:querystring""node:stream""node:string_decoder""node:url""node:util""node:util/types""node:zlib""node-fetch"
Elapsed: 131ms | User: 121ms | Sys: 29ms
RSS: 1.07GB | Peak: 131.57MB | Commit: 1.07GB | Faults: 0
panic(main thread): Segmentation fault at address 0x0
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
To send a redacted crash report to Bun's team,please file a GitHub issue using the link below: https://bun.report/1.1.17/lr1bb66bbaAqqggsE2lnhnE+wjQuyk+9Dusp/9Dgko/9Dys/g+Do6u4gFms424E0mv14E4nt74EA2AAfish: Job 1, 'bun run main.js' terminated by signal SIGILL (Illegal instruction)
Stack Trace (bun.report)
Bun v1.1.17 (bb66bba) on linux x86_64 [RunCommand]
How can we reproduce the crash?
The command i executed:
Relevant log output
Stack Trace (bun.report)
Bun v1.1.17 (
bb66bba
) on linux x86_64 [RunCommand]Segmentation fault at address 0x00000000
ld-temp.o:0
:WTF::Unicode::convertReplacingInvalidSequences
??
PropertyTable.h:332
:WTF::ASCIILiteral JSC::JSObject::putDirectInternal<(...)1>
Identifier.h:53
:JSC::JSValue JSC::JSObject::getIfPropertyExists<JSC::Identifier>
PropertyTable.h:322
:JSC::JSValue JSC::JSObject::getIfPropertyExists<JSC::Identifier>
Function.h:38
:Zig::GlobalObject::GlobalObject
ld-temp.o:0
:JSC::ErrorInstance::getOwnPropertySlot
ld-temp.o:0
:JSC::Heap::runEndPhase
ld-temp.o:0
:JSC::Heap::runNotRunningPhase
ld-temp.o:0
:JSC::Heap::didAllocate
The text was updated successfully, but these errors were encountered: