Able to repro this issue on Windows 7, MAC (10.11.6) & Ubuntu Trusty (14.04) for Google Chrome Stable Version - 53.0.2785.89

This is a Non-Regression issue existing from M30 - # 30.0.1549.0

I can't reproduce but this seems suspicious anyhow. Worth look
The best I could get is that the i didn't get an alert, it just passively hung until i refreshed (and then it hit me with the alert)

(hopefully) Repro Steps:

* use stable
* open https://output.jsbin.com/fuwezu/1/quiet
* open devtools
* async checkbox on, paused on exceptions on, paused on caught on.
* reload page
* step in
* step in
 --- hangs ---

einbinder, wanna take a look? 

(on ToT, i had no hanging problem.)
rnimmagadda can you confirm if you can repro in tot/canary ?

I don't get the crash, I get it hanging and then an alert if I reload again. Windows 10 Chrome 53

@paulirish: Re-test the same on MAC (10.11.6) for Chrome Latest Canary Version - 55.0.2857.0 and observed the same result.

Screen-recording is attached.

Deleted: 644592.mov 11.1 MB

644592.mov 11.1 MB Download

Could you describe in details what when wrong on your screen cast? It looks good for me.

@kozyatinskiy: I'm observing the same output in the console for Chrome Latest Stable Version - 53.0.2785.101 & Chrome Version - 30.0.1549.0 for Windows 7, MAC (10.11.6) & Ubuntu Trusty (14.04) OS.

Based on this I have marked it as Untriaged.

Thank you.

Deleted: Console Output.png 11.5 KB

	Console Output.png 11.5 KB View Download

I could reproduce it with steps from #2. In beta and ToT it works fine.
There is one problem with our injected_script_source.js. If you run code:
for (var i = 0; i < 1000; ++i)
Array.prototype.__defineSetter__(i + "",() => {throw new Error()});

DevTools will work incorrectly for many many things in console. We'll fix this during migration injected_script_source.js into native code.

I think that we can mark this as Fixed.

Bulk closing low-priority issues with no activity. Please re-file and refer to the closed issue if it's essential to fix.