Closed Bug 1434386 Opened 8 years ago Closed 7 years ago

debugger random breakpoints

Categories

(DevTools :: Debugger, defect)

58 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: byja, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:58.0) Gecko/20100101 Firefox/58.0 Build ID: 20180128191252 Steps to reproduce: Load a page, with linked "someCode.js" file which is longer than 3000+ lines Open DEV tools in a separate window. Select "Debugger" tab Set breakpoint in "someCode.js" on line number > 2500 Run code, debugger kicks in, everything works as expected. No changes made in "someCode.js" file Refresh the page (CMD+R) Actual results: Debugger window pane is redrawn, and sometimes file "someCode.js" is loaded with scroll point is in place (line number > 2500), but sometimes only file is loaded, sometimes it is not. Sometimes it scrolls to breakpoint line, but sometimes not. Random breakpoints are inserted on lines < 300 Actual breakpoint on line number > 2500 is not set. Same behaviour regardless where the DEV window is (docked or windowed) Expected results: If only breakpoint was set on line number 2567, when page is refreshed, Debugger should show line 2567 If code was not changed (no white space, no unbreakable lines with control brackets, etc.) Breakpoint should be set and active on line 2567. There should be no other random breakpoints introduced. Error noticed since v57
Component: Untriaged → Developer Tools: Debugger
Latest release 58.0.2 seems to have cleared the bug. Breakpoints remain where they're set. Reload behaves as it should: either keeps the current breakpoint line, or disables it if control char or white space is introduced. Debugger now correctly offsets the scroll position in source code pane (under Debugger tab) Still testing, but it now seems fine.
Thanks Vuk, it would help if you could create an example with our glitch template http://dbg.glitch.me/ or some other way.
Product: Firefox → DevTools

this should work now. Please let me know if you still see issues.

Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.