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

Web (online) debugger is completely unresponsive while consuming 100% CPU (1 core) #15715

Open
efogdev opened this issue Dec 11, 2024 · 0 comments
Labels
bug Something isn't working debugger Something to do with `bun --inspect` or the debugger

Comments

@efogdev
Copy link

efogdev commented Dec 11, 2024

What version of Bun is running?

1.1.38

What platform is your computer?

Linux 6.12.4-1-cachyos x86_64 unknown

What steps can reproduce the bug?

  1. Start app with bun --inspect=0.0.0.0:13010/debug --watch src/index.ts
  2. Open debug.bun.sh/#localhost:13010/debug

What is the expected behavior?

Actual debugger is working at least a little

What do you see instead?

Debugger UI is stuck in "console" tab and completely unresponsive, probably in some infinite loop

Additional information

Comprehensive 1-minute video: https://www.youtube.com/watch?v=EGJ5a-5caX8
The browser is clean installation of Chromium (also tried in my Vivaldi, same result)
It's driving me nuts because I can't build the debugger because it's really far off my tech stack and I don't have Mac
I'm under GNOME 47 Wayland, OS is arch linux, fully updated

@efogdev efogdev added bug Something isn't working needs triage labels Dec 11, 2024
@nektro nektro added debugger Something to do with `bun --inspect` or the debugger and removed needs triage labels Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working debugger Something to do with `bun --inspect` or the debugger
Projects
None yet
Development

No branches or pull requests

2 participants