New issue
Advanced search Search tips

Issue 888261 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 4
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Variables local to current scope show as undefined

Reported by rocca.jo...@gmail.com, Sep 22

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36

Steps to reproduce the problem:
This is not a great bug report because I am unable to reproduce it consistently. It only occurs when using the debugger - the code itself actually runs fine. It's as if devtools thinks all my variables are out of scope when they're not.

What is the expected behavior?

What went wrong?
Have a look at this video:

https://i.imgur.com/lmhKJoP.mp4

Notice that every local variable is showing as undefined. And notice that the debugger statement should only have triggered if the two variables were different. So devtools is lying about them being both undefined.

It's also impossible for `Number(...)` to return undefined, so that's just extra evidence that devtools is wrong here.

Did this work before? N/A 

Chrome version: 69.0.3497.81  Channel: n/a
OS Version: 16.04
Flash Version: 

I have also tested this on Chrome 70.0.3538.16 (Official Build) beta (64-bit). I get the same result.

If I can get around to stripping down my code to try to get a minimal example, I will, but I might not be able to.
 
Labels: Needs-Triage-M69
Components: -Platform>DevTools Platform>DevTools>JavaScript
Owner: kozy@chromium.org
Status: Assigned (was: Unconfirmed)
Thanks for you report. Looks broken. Do you use source maps? If you try to evaluate this variable in console will it return real value? Do you use arrow functions?
Could you try to extract this function and attach it to the bug?
Status: WontFix (was: Assigned)
Unfortunately, there is no enough information to investigate this issue further. It looks like some Source Map + our smart SourceMapNameResolver logic issue but I can not reproduce it.
Feel free to file another issue if you still can reproduce it and thanks for your report!

Sign in to add a comment