Issue metadata
Sign in to add a comment
|
Breakpoints disappear if same file is launched as WebWorker
Reported by
danielk...@gmail.com,
Mar 4 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Steps to reproduce the problem: 1. Open https://fiddle.jshell.net/danielku15/nrgqtja6/show/ as example and launch the developer tools. 2. Set a breakpoint on AlphaTab.js Line 3783 (ReadScore function) 3. Refresh the page 4. Debugger properly breaks as expected. 5. Let the debugger continue. 6. Suddenly the Developer Tools flicker (reload?) 7. The breakpoints are gone. What is the expected behavior? The breakpoints must not be cleared and be active for all workers and the UI thread. What went wrong? I have the feeling that the main reason is that the script file.js is included in the main page and also launched via WebWorker. The WebWorker launch seems to trigger some refresh on the developer tools which also clears all breakpoints. Did this work before? Yes 57.0.2987.110 Chrome version: 64.0.3282.167 Channel: stable OS Version: 10.0 Flash Version: Tested on BrowserStack Windows 10, Chrome 57 was still working, Chrome 58 not. This bug currently drives me crazy as I cannot properly debug my project.
,
Mar 5 2018
Thanks for filing the issue! Checked the issue on reported chrome version 64.0.3282.167 using Windows 10 with the below mentioned steps. 1. Launched Chrome 2. Navigated to https://fiddle.jshell.net/danielku15/nrgqtja6/show/ 3. We have Set a breakpoint on AlphaTab.js Line 3783 4. Refreshed the page On the reported chrome version we didn't observe any flickering in DevTools, though the break point is gone after page refresh. Attaching the screen cast of the latest chrome version, where- after refreshing the page the break point is still there. @Reporter: Could you please have a look at the screen cast and let us know the attached video has an issue or working as expected, your feedback helps us to triage the issue further in a better way.
,
Mar 5 2018
Looks like you picked the wrong file for the exact reproduction of my steps. The file for the breakpoint is "AlphaTab.js" not "AlphaSynth.js" (two libraries of the same product, easy to confuse) that's why it did not break on refresh. I attached a screen cast of my reproduction.
,
Mar 5 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 5 2018
,
Mar 6 2018
I fixed this bug recently. Fix should be available starting M66. Please try Google Chrome Canary. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sindhu.chelamcherla@chromium.org
, Mar 4 2018