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

Steps to reproduce the problem:
This new feature is really very useful, but I think that it could be improved a bit to make it easy to use.

There are two problems that I see:

1. If the dev tools is closed, you can't open it directly by pressing F12 (even if you use the Chrome menu to load the dev panel, it just not works).

Suggestion: I (maybe) understand that F12 will not works because that the Chrome try check if some event handle this key (like onkeydown), but because the page is freezed on infinity loop, then the F12 is never processed. I think that after 1 freeze second the Chrome should understand that app is not respoding, so F12 should call dev tools.

--

2. The feature is very hidden. You should first stop script execution, then hold resume button, then stop again.

Suggestion: after 1 freeze second, Chrome should understand that app is not responding and display a console.log() something like "Looping running on script.js:14 seems to be infinity" and with a option to "force stop". If loop ends, then this log should be hide.

--

Maybe to detect if loop is freezed, Chrome should wait 1 second or a bit more and check if loop expression variables is modifying a long of time. If it is not changing, then could consider loop infinity and make item 1 and 2 suggestions available. If Chrome could not identify a infinity loop, then wait about 5~10 seconds and identify anyway.

What is the expected behavior?

What went wrong?
-

Did this work before? N/A 

Chrome version: 67.0.3396.18  Channel: beta
OS Version: 10.0
Flash Version: