Skip to content
New issue

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

Inspect crashed with illegal hardware instruction #15420

Open
saicharan-kandukuri opened this issue Nov 26, 2024 · 2 comments
Open

Inspect crashed with illegal hardware instruction #15420

saicharan-kandukuri opened this issue Nov 26, 2024 · 2 comments
Labels
crash An issue that could cause a crash linux An issue that occurs on Linux runtime

Comments

@saicharan-kandukuri
Copy link

saicharan-kandukuri commented Nov 26, 2024

How can we reproduce the crash?

I got this error when i was spam refreshing debug.bun.sh for my bun project and after that --inspect does not work on any of my bun projects it either shows below error in site or crashes in terminal with panic: Illegal instruction at address 0x59443CD.

Image

Relevant log output

============================================================
Bun v1.1.34 (5e5e7c60) Linux x64
Linux Kernel v6.9.3 | glibc v2.35
CPU: sse42 popcnt avx avx2
Args: "bun" "--inspect" "index.ts"
Features: Bun.stderr Bun.stdin(2) Bun.stdout WebSocket(2) dotenv(2) fetch(3) http_server(2) jsc spawn(2) tsconfig(9) tsconfig_paths
Builtins: "bun:main" "bun:sqlite" "node:async_hooks" "node:buffer" "node:child_process" "node:crypto" "node:events" "node:fs" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:perf_hooks" "node:process" "node:querystring" "node:stream" "node:string_decoder" "node:tls" "node:tty" "node:url" "node:util" "node:util/types" "node:zlib" "node:worker_threads" "ws" "node-fetch" "node:http2" "node:diagnostics_channel"
Elapsed: 10928ms | User: 3132ms | Sys: 661ms
RSS: 0.87GB | Peak: 0.32GB | Commit: 0.87GB | Faults: 0

panic(main thread): Illegal instruction at address 0x5951A4D
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.34/la15e5e7c6Ajv76/9B+xyQu18lyFwqzn5Eu1+m5E8n27iFisv+7Dwlgt+Dgu+loDy/q5+Cq/o28CA3A6kt0yF

[1]    88418 illegal hardware instruction (core dumped)  bun --inspect index.ts

Stack Trace (bun.report)

Bun v1.1.34 (5e5e7c6) on linux x86_64 [AutoCommand]

Illegal instruction at address 0x05951A4D

  • ??
  • ld-temp.o:0: bmalloc_heap_config_specialized_try_deallocate_not_small_exclusive_segregated
  • ld-temp.o:0: JSC::IsoInlinedHeapCellType<JSC::JSString>::finishSweep
  • ld-temp.o:0: JSC::MarkedBlock::Handle::sweep
  • ld-temp.o:0: JSC::LocalAllocator::tryAllocateIn
  • ld-temp.o:0: JSC::LocalAllocator::allocateSlowCase
  • LocalAllocatorInlines.h:41: JSC::JSString::create
  • JSString.h:963: WTF::Detail::CallableWrapper<Bun::BunInspectorConnection::sendMessageToDebuggerThread(...)::'lambda'(...), void, WebCore::ScriptExecutionContext&>::call
  • Function.h:82: Bun__performTask
  • event_loop.zig:300: src.bun.js.event_loop.EventLoop.tickQueueWithCount__anon_141007

Features: Bun.stderr, Bun.stdin, Bun.stdout, WebSocket, dotenv, fetch, http_server, jsc, spawn, tsconfig, tsconfig_paths, tsconfig_paths

@saicharan-kandukuri saicharan-kandukuri added the crash An issue that could cause a crash label Nov 26, 2024
@github-actions github-actions bot added linux An issue that occurs on Linux runtime labels Nov 26, 2024
Copy link
Contributor

@saicharan-kandukuri, thank you for reporting this crash. The latest version of Bun is v1.1.37, but this crash was reported on Bun v1.1.34.

Are you able to reproduce this crash on the latest version of Bun?

bun upgrade

For Bun's internal tracking, this issue is BUN-8YQ.

@saicharan-kandukuri
Copy link
Author

Was able to recreate this on v1.1.37 too.
Bun v1.1.37 (8ca0eb8) on linux x86_64 [AutoCommand]

Illegal instruction at address 0x059443CD

  • ??
  • ld-temp.o:0: bmalloc_heap_config_specialized_try_deallocate_not_small_exclusive_segregated
  • ld-temp.o:0: JSC::IsoInlinedHeapCellType<JSC::JSString>::finishSweep
  • ld-temp.o:0: JSC::MarkedBlock::Handle::sweep
  • ld-temp.o:0: JSC::LocalAllocator::tryAllocateIn
  • ld-temp.o:0: JSC::LocalAllocator::allocateSlowCase
  • LocalAllocatorInlines.h:41: JSC::JSString::create
  • JSString.h:963: WTF::Detail::CallableWrapper<Bun::BunInspectorConnection::sendMessageToDebuggerThread(...)::'lambda'(...), void, WebCore::ScriptExecutionContext&>::call
  • Function.h:82: Bun__performTask
  • event_loop.zig:300: src.bun.js.event_loop.EventLoop.tickQueueWithCount__anon_142118

Features: Bun.stderr, Bun.stdin, Bun.stdout, WebSocket, dotenv, fetch, http_server, jsc, spawn, tsconfig, tsconfig_paths, tsconfig_paths

I was using it in firefox but when i used in chrome its working fine.
Guess imma use chrome for some time.
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crash An issue that could cause a crash linux An issue that occurs on Linux runtime
Projects
None yet
Development

No branches or pull requests

1 participant