panic(main thread): Segmentation fault at address 0x0

rootfebri commented 1 month ago

How can we reproduce the crash?

I'm not quite sure but this happens quite often, I try to run bun --bun run tauri dev

Relevant log output

No response

Stack Trace (bun.report)

Bun v1.1.12 (43f0913) on linux x86_64 [RunAsNodeCommand]

Segmentation fault at address 0x00000000

ld-temp.o:0: WTF::jscSignalHandler
??
path_watcher.zig:660: src.bun.js.node.path_watcher.PathWatcher.deinit
path_watcher.zig:910: src.bun.js.node.node_fs_watcher.FSWatcher.close
node_fs_watcher.zig:549: src.bun.js.node.node_fs_watcher.FSWatcher.FSWatchTaskPosix.run
event_loop.zig:1026: src.bun.js.event_loop.EventLoop.tickQueueWithCount__anon_363392
event_loop.zig:1249: src.bun.js.event_loop.EventLoop.tick
javascript.zig:1275: src.bun.js.javascript.OpaqueWrap__anon_53035__struct_285774.callback
bindings.cpp:4660: JSC__VM__holdAPILock
shimmer.zig:186: src.bun_js.Run.boot

github-actions[bot] commented 1 month ago

@rootfebri, the latest version of Bun is v1.1.20, but this crash was reported on Bun v1.1.12.

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

bun upgrade

rootfebri commented 1 month ago

Yes, it's upgradeable. The crash is barely happen, right now Im working on webview app and I tried to open frontend in chrome and webview (main app) and I try to close the main app but chrome still listening to dev connection and node frozen that makes my main app can't relaunch because the port is locked by node. I try to kill node process with SIGTERM but it doesn't work so I try with SIGKILL then the next time I relaunch main app it crashed like that. Is it still relevant to bun's current version?

rootfebri commented 1 month ago

Also, can you take a look into this? https://github.com/tailwindlabs/tailwindcss-intellisense/issues/1021#issuecomment-2239246960

lizhongyue248 commented 3 weeks ago

Is there any follow-up on this issue?

oven-sh / bun