4 ms·
Right click on the line number (of the debugger statement), and select "Never pause here". You'll need to do that for each statement.
by jenscow 5y ago
Right click on the line number (of the debugger statement), and select "Never pause here". You'll need to do that for each statement.
- rasz 5y agoThe trick is you never know where debugger was really called from, try it https://9anime.to/watch/a-certain-magical-index-dub.l1kn/ep-1 https://9anime.to/watch/a-certain-magical-index-dub.l1kn/ep-... You can bypass this by killing setintervals altogether.
- thrdbndndn 5y agoI actually managed to bypass this without destroying `setInterval()`. After a few times clicking "continue", Chrome showed me where the debugger line is in a VM script. And then I can disable it as OP said.
- thrdbndndn 5y agoWow, never knew this. Thanks!