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

Steps to reproduce the problem:
1. Build your JavaScript and CSS and use sourcemaps
2. Keep devtools open & develop on a site (using hot reload, happens without too)
3. After the earth rotates a fraction of a degree, the sourcemaps stop working, and all I see is bundle.js:someuselesslinenumber. When this happens, React devtools (by Facebook) also stops working, and simply sits at "Looking for React" forever. 
4. Restarting devtools temporarily fixes the problem

What is the expected behavior?
That the devtools wouldn't crash 15 to 30 times in an hour. 

What went wrong?
The source maps stop working randomly, sometimes a hot reload triggers it, sometimes they work for a few seconds and then crash, sometimes there's no problems. 

Did this work before? No 

Chrome version: 60.0.3112.90  Channel: stable
OS Version: Arch Linux
Flash Version: 

Sourcemaps have always been buggy as hell. I don't think that they've ever worked without a hitch. I've had the sourcemap problem on Windows, OSX, and three different Linux distributions for many years. Different accounts, different sets of extensions, nothing in common to connect. 

The sourcemap crash isn't related to a spesific build tool either, I've used sass & stylus directly, through grunt & gulp, and the last two years I've used Rollup and Webpack to bundle JavaScript. 

Better screenshots: https://github.com/facebook/react-devtools/issues/965
 

Deleted: Selection_357.png 19.5 KB

	Selection_357.png 19.5 KB View Download