Issue metadata
Sign in to add a comment
|
Inconsistent debugger pause behaviour on BP sliding
Reported by
sandroto...@googlemail.com,
Sep 26
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 Steps to reproduce the problem: 1. Open "min.html" 2. Set BPs as shown in "devtools.mkv" What is the expected behavior? The debugger should either stop or skip over the BP in line 3, regardless of whether the BP is directly set in line 3 or moved there automatically. What went wrong? The pause behaviour of the debugger is inconsistent. Did this work before? Yes v68 on Arch Linux did not exhibit this behaviour, the debugger did not pause at the BP. Chrome version: Version 69.0.3497.100 (Official Build) Channel: stable OS Version: Arch Linux x64 Flash Version: n/a
,
Sep 27
Tried to reproduce the on reported chrome 69.0.3497.100 using Ubuntu 14.04. Attaching screencast for reference. Steps: ---- 1. Launched reported chrome 2. Downloaded given file and dropped on new tab 3. Navigated to Dev tools > Source 4. Set Breakpoint as per given video file and clicked on f5 As we are observed it skips line 3 and moved to line 4 @Reporter: Could you please check the attached screen cast and please let us know if anything missed from our end and Can you verify this issue with fresh profile that is not having any extensions and apps or reset all the flags. Let us know whether issue still persists. Thanks..!
,
Sep 27
I'm sorry, I'm not really sure what your question is. Could you clarify? I can't really tell what actions you are executing in the screen recording because of massive glitches, but from your description I gather that you are setting the BP in line 3 and then hitting continue (after being stopped at the BP in line 1) and the debugger halts at the BP in line 4, which would be consistent with what I'm seeing. The issue is that if you instead set the BP in line 2 instead of 3 (after which it is moved to line 3), and then hit continue, the debugger halts at line 3.
,
Sep 27
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
,
Sep 28
sandrotolksdorf@ Thanks for the feedback... As per comment #0 and comment #3, retried the issue on reported chrome 69.0.3497.100 using ubuntu 14.04. As we are unable reproduce the issue from our end, hence requesting someone from Platform>DevTools team to look in to it and Removing Needs-Bisect label to it. Thanks..!
,
Oct 8
This looks like a real bug indeed. Thank you for filing! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by vamshi.kommuri@chromium.org
, Sep 26