Open marvinside opened 1 year ago
I'm not able to reproduce this on macOS arm64
i not sure this related or not, but when i click record timeline, seg fault occurs
steps:
bun --inspect any.ts
debug.bun.sh
bun version: 1.0.7+b0393fba6200d8573f3433fb0af258a0e33ac157
os: Linux 5.15.90.1-microsoft-standard-WSL2 x86_64 unknown
I found another steps to reproduct seg fault, which is when the debugger open when the application is already running, any action on debugger will trigger the seg fault
bun --inspect-brk any.ts
debug.bun.sh
This bug also occurs when opening the debugger on a running express app.
Steps to reproduce:
bun init
bun add express @types/express
// index.ts
import express, { Express } from 'express'
const app = express()
app.get('/', (req, res) => { res.send('Hello World!') })
app.listen(3000, () => { console.log('[server]: Server is running at http://localhost:3000') })
4. Run `bun --inspect index.ts`
5. Open the debugger and do anything
The result is a segmentation fault error.
UPDATE: This only occurs with `--inspect`, but works with `--inspect-brk`. Maybe this is an unrelated issue.
I have no idea what happened since 28th Feb, but I do not get any more segfaults with the inspector, however I am still on bun 1.0.29+a146856d1
Just upgraded, now on revision 1.1.24+85a329911, seems to work too
Ticket can be closed for me, but it seems more people are affected.
@parkernilson @eslym Can you check if you still have issues?
What version of Bun is running?
(Edit: added more affected Versions)
What platform is your computer?
Darwin 22.6.0 x86_64 i386
What steps can reproduce the bug?
Testfile:
Run
bun --inspect-brk ./src/debug2.ts
, then open the debugger link in the browserWhat is the expected behavior?
Debugger should load, bun should continue running
What do you see instead?
Additional information
running without
--inspect-brk
works.