-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Inspector causes Rust runtime crash #5807
Comments
@sug0 Could you share the full stack trace? |
Sure, but it doesn't help much, I'm not on a debug build, this build has no symbols. In any case, it's fairly easy to reproduce:
The stack trace of the release build is the following:
|
More useful stack trace below.
|
…enoland#5822) Note that this does not fix the 'Uncaught ReferenceError' issue that happens when 'eager evaluation' is enabled in the inspector. Fixes: denoland#5807
…enoland#5822) Note that this does not fix the 'Uncaught ReferenceError' issue that happens when 'eager evaluation' is enabled in the inspector. Fixes: denoland#5807
…enoland#5822) Note that this does not fix the 'Uncaught ReferenceError' issue that happens when 'eager evaluation' is enabled in the inspector. Fixes: denoland#5807
…enoland#5822) Note that this does not fix the 'Uncaught ReferenceError' issue that happens when 'eager evaluation' is enabled in the inspector. Fixes: denoland#5807
…enoland#5822) Note that this does not fix the 'Uncaught ReferenceError' issue that happens when 'eager evaluation' is enabled in the inspector. Fixes: denoland#5807
Trying to call functions within
Deno
on the inspector console, runningdeno repl --inspect
, causes a crash, due to a cell already being borrowed, as seen here:The culprit of the crash seems to be this line of code:
https://github.com/denoland/deno/blob/master/cli/inspector.rs#L547
Which keeps the cell borrowed, while
poll_sessions
is called, for instance here:https://github.com/denoland/deno/blob/master/cli/inspector.rs#L367
Edit: forgot to mention
deno 1.0.2
v8 8.4.300
typescript 3.9.2
The text was updated successfully, but these errors were encountered: