Debugger does not stop at breakpoint
Reported by
lars.bau...@gmail.com,
Jul 26 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: I have created an example here: https://stackoverflow.com/q/45305184/3579095 1. Run the snippet from stackoverflow in chromium 2. Open dev tools 3. Drag an image from another website in the drop area What is the expected behavior? The debugger should stop at the breakpoint everytime it executes the line of code. What went wrong? The debugger stops only one time. But the console output shows it was executed three times. Did this work before? N/A Chrome version: 59.0.3071.115 Channel: n/a OS Version: 59.0.3071.115 Flash Version:
,
Jul 27 2017
Alexey, can you repro this? I wasn't able to.
,
Aug 31 2017
Chrome Version 60.0.3112.113 (Official Build) (64-bit), macOS Sierra 10.12.6 (16G29)
,
Oct 11 2017
I created a stackoverflow question (https://stackoverflow.com/questions/46674214/chrome-javascript-event-loop-not-paused-on-debugger), but then I found this bug. There is something really screwed up going on with chrome javascript. Its supposed to be single threaded or at least act that way, but I get the feeling that all the things done in the name of throttling have made some big mistakes. In the attached file, if you have DevTools open it should break after 10 seconds (which it does) but at the same time its still running and outputting more console messages. Chrome Version 61.0.3163.91 (Official Build) (64-bit)
,
Oct 16 2017
,
Dec 5 2017
Original issues is fixed in ToT and latest Canary, feel free to reopen this issue if you still can reproduce it. For #5, worker is running in separate thread, you can select this thread in DevTools sources panel and pause it as well if needed. All console messages will be dumped to console as soon as you resume main page. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ligim...@chromium.org
, Jul 26 2017