Breakpoints stop working after reloading a page via ST3/SWI

[neilalex]

What I’m seeing

• If I press Ctrl + Shift + R and choose ‘Reload’ (or if I use reload_on_save), Chrome proceeds to refresh the page, yet no longer stops at any breakpoints until I stop debugging, start debugging again, clear all existing breakpoints, and then re-create them

• The issue does not seem to occur if I refresh by pressing F5 in Chrome itself – SWI will continue to stop at existing breakpoints

  • (However, if I reload a page via the ST3/SWI command, subsequently pressing F5 does not appear to resurrect any breakpoints. The only apparent solution after using SWI reload is to stop debugging and start again.)

• Note that I don’t get any console errors, even in debug mode

  • (Well, I do get the message “Error from debuggee: ‘Page.setOverlayMessage’ wasn’t found… but that seems to be a separate issue. I can comment out all webkit.Debugger.setOverlayMessage lines, which removes this error, yet the above issue still occurs.)

Steps I’ve tried in addressing it so far

• I thought perhaps breakpoints were becoming “deactivated” on reload – I understand that sometimes this will happen with the browser's Dev Tools, if the “Preserve log” box is not checked (see stackoverflow).

• So, I tried calling channel.send(webkit.Debugger.setBreakPointsActive(True)) before and after every time webkit.Page.reload() is called. (Note, to be able to do this I added a setBreakPointsActive function to webkit/Debugger.py.)

• I also tried adding channel.send(webkit.Debugger.setSkipAllPauses(False)) before and after every call to webkit.Page.reload(). I saw that the solution to Reload page does not work correctly #99 does this to address a similar problem.

• Inside webkit/Page.py, I added the ignoreCache argument (trying both True and False as values) to the Page.reload command, in case that makes a difference

• I commented out every instance of "channel.send(webkit.Network.clearBrowserCache())" I could find

• None of these approaches seemed to help

I’m using Windows 10, Chrome 7.0.2987.133 (64-bit, the latest non-Canary), ST3 build 3126, SWI releases 1.7.4 and 1.7.5 (all issues occur for me in both)