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

deno crashes randomly on startup using --inspect-wait #28311

Open
rajinder-yadav opened this issue Feb 26, 2025 · 0 comments
Open

deno crashes randomly on startup using --inspect-wait #28311

rajinder-yadav opened this issue Feb 26, 2025 · 0 comments
Labels
debugger Chrome DevTools inspector/debugger integration

Comments

@rajinder-yadav
Copy link

Version: Deno 2.2.2

$ uname -a
Linux source 6.13.1-1-default #1 SMP PREEMPT_DYNAMIC Mon Feb  3 05:33:25 UTC 2025 (1918d13) x86_64 x86_64 x86_64 GNU/Linux

I get random crashes when using --inspect-wait on Linux (openSUSE TW):

Task debug deno run --inspect-wait --watch --allow-all ./src/app.ts
Watcher Process started.
Debugger listening on ws://127.0.0.1:9229/ws/d09785d0-8b1b-4eb6-a493-e55f93a2c282
Visit chrome://inspect to connect to the debugger.
Deno is waiting for debugger to connect.

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: linux x86_64
Version: 2.2.2
Args: ["/home/yadav/.local/share/pnpm/global/5/.pnpm/[email protected]/node_modules/deno/deno", "run", "--inspect-wait", "--watch", "--allow-all", "./src/app.ts"]

thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_core-0.338.0/inspector.rs:381:16:
internal error: entered unreachable code
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Using RUST_BACKTRACE=1

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: linux x86_64
Version: 2.2.2
Args: ["/home/yadav/.local/share/pnpm/global/5/.pnpm/[email protected]/node_modules/deno/deno", "run", "--inspect-wait", "--watch", "--allow-all", "./src/app.ts"]

thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_core-0.338.0/inspector.rs:381:16:
internal error: entered unreachable code
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic
   3: deno_core::inspector::JsRuntimeInspector::poll_sessions
   4: deno_runtime::worker::MainWorker::evaluate_module::{{closure}}
   5: deno::worker::CliMainWorker::execute_main_module::{{closure}}
   6: deno::worker::CliMainWorker::run_for_watcher::{{closure}}
   7: deno::tools::run::run_script::{{closure}}
   8: deno::spawn_subcommand::{{closure}}
   9: tokio::runtime::task::raw::poll
  10: deno::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
@marvinhagemeister marvinhagemeister added the debugger Chrome DevTools inspector/debugger integration label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debugger Chrome DevTools inspector/debugger integration
Projects
None yet
Development

No branches or pull requests

2 participants