UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
1. Use the 'inspect' link on `chrome:inspect` to view the console output of a website running on Android. Make sure this website uses source maps.
2. Get the website to log an exception via `console.error`. In the Developer Tools, the corresponding log line can be expanded to show a stack trace (see `before.png`). Each element of the stack trace contains a file name and line number. As expected, Chrome uses the source map to list the file and line for the *original* files, not for the bundled output. Notice how the stack trace lists `console.js:64`, then `logger.js:102`, and so on.
3. Close the Developer Tools window, then immediately re-open it by clicking 'inspect' again.
4. The log line we just saw has collapsed. Re-expand it to show the stack trace again. Note that *this is the same stack trace we saw before*, we're merely expanding it for the second time.

What is the expected behavior?
I'd expect the stack trace to be displayed exactly as before, using the source map.

What went wrong?
The stack trace now looks different than before (see `after.png`). The function names are identical, but the file names and line numbers have changed. They now say `code.js:106614`, `code.js:106863`, and so on. The stack trace has "forgotten" the source map and instead shows the positions within the bundled output.

Did this work before? N/A 

Chrome version: 60.0.3112.90  Channel: n/a
OS Version: OS X 10.11.6
Flash Version:
 

Deleted: before.png 142 KB

	before.png 142 KB View Download

Deleted: after.png 149 KB

	after.png 149 KB View Download