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

Steps to reproduce the problem:
1. Implement a loop where you call "debugger;"
2. launch page
3. Open console
4. you are stuck

What is the expected behavior?
The behaviour is obvisously good, but there should be a way to ignore this 
Like with alert box, it can be a mistake or someone messing with my console

What went wrong?
Console is locked up in a loop

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 10.0
Flash Version: 

This page is a spam/scam
it does not contain a virus or something it just gather data and force share at the end of the form (nothing really interesting)

The code is attached later in this text and also in the screenshot, 
you don't have to click the link in anyway, it's just for reference
http://nespr esso.com-rebajas.info/en-xx/

But the scammer used a loop where he called the debugger; method, leaving the console unusable.

// THE WHOLE CODE IS HERE FOR REFERENCE
setTimeout(function() {
    try {
        (function b(i) {
            if (('' + (i / i)).length !== 1 || i % 20 === 0) {
                (function() {}
                ).constructor('debugger')();
            } else {
                debugger ;
            }
            b(++i);
        }
        )(0);
    } catch (e) {}
}, 0);

I think there should be an option to ignore some "debugger;" breakpoint, as this behaviour is mostly used to kill the developper's browser.
 

Deleted: Screenshot_407.png 87.5 KB

	Screenshot_407.png 87.5 KB View Download