UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36

Steps to reproduce the problem:
Go to the sources tab on a piece of compiled code (in my case using Babel and Webpack) that has source maps, put a breakpoint on a line and look at the variables in the scopes section.

What is the expected behavior?
The names of the variables were always wrong in the sense that they followed the real names in the source code instead of the source maps. However, recently, they seem to have gotten totally screwed up.

What went wrong?
As you can see in my screenshot of the dev tools, the name of all variables in one of the scopes is "Text". This is very strange and it happens in every file. It's not always "Text" though. In every file, a random name is picked and used by the debugger for loads of different variables within that file while debugging it.

This doesn't seem to be an issue in Chrome 56.0.2915.0 canary (64-bit), but it is on the latest stable build.

Did this work before? Yes 

Chrome version: 54.0.2840.99  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0
 

Deleted: chrome-debugger-variables-wrong-name.jpg 47.2 KB

	chrome-debugger-variables-wrong-name.jpg 47.2 KB View Download