I've tried to uninstall and reinstall too.
It works for the first time. Subsequent tries reproduce the issue. Haven't been able to debug and is a big problem for developers :(

Unable to reproduce the issue on Win-10 using chrome reported version #56.0.2924.87 and latest canary #58.0.3014.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened google search page.
2. Opened developer tools, navigated to Sources section and placed few breakpoints in a .js file.
3. Refreshed the page.
4. Observed that breakpoints retained and stopped at the breakpoint for debugging.

hardhikm@ - Could you please verify the screencast and please let us know if anything missed from our side.

Also could you please check this issue on latest canary #58.0.3014.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Deleted: 692897.mp4 5.9 MB

	692897.mp4 5.9 MB View Download

Thank you Rajshree for the investigation.

I am able to put breakpoints and debug on sites other than the ones hosted in my own machine.

Thank you for your report.  Could you please help us investigate by sending a small file to reproduce the behavior?  If you have a sample file/folder of code that you are willing to share, it would go a long way to help us investigate.

I am having the same issue which I first noticed yesterday, despite it working just fine for the last year. 

It is also only happening for local files, the breakpoints in functions etc won't stick after a refresh. 

Setting a "first time parsing" breakpoint in global scope seems to pause execution on refresh at the appropriate line, but the breakpoint won't be listed under "breakpoints" and refreshing again leads to no pausing.


I thought I was going crazy because I couldn't find any similar issues when searching online, it's a huge relief to see someone else reporting the same issue here, it's not just me.


I am using Google Chrome Version 56.0.2924.87 on Windows 8.1 Enterprise x64

I tried reproducing this in a minimal way.

Adding a non-existent sourceMap seems to cause the breakpoints to clear on a refresh.

Look at the two attached files. Set a breakpoint on the local JS file, and notice that it is gone when you refresh.

If you remove the 
//# sourceMappingURL=/path/to/file.js.map
from the breakpoints_lost.js file then the breakpoints will remain on a refresh.

Deleted: breakpoints_lost.html 202 bytes

breakpoints_lost.html 202 bytes View Download

Deleted: breakpoints_lost.js 104 bytes

breakpoints_lost.js 104 bytes View Download

Unable to reproduce in 

Version 58.0.3019.0 (Official Build) canary (64-bit)

I tried both my breakpoints_lost.html/js example AND my real world scenario in the canary version above, and everything is working properly. The breakpoints remain after a refresh in both.

So it seems to have been fixed in canary at least.

I am also seeing this issue, but only on some pages. See attached gif.

OS: Windows 10
Chrome: 56.0.2924.87 (Official Build) (32-bit)

Steps to reproduce:
1. Navigate to https://360inspecthub.com/ims/resources/index.html
2. Open Chrome Dev Tools
3. Go to the Sources tab
4. Open file all.js
5. Place a breakpoint at any line. I tested lines 32, 314, and 95559.
6. Refresh the page by clicking the Refresh icon next to the back/forward arrows.
7. Continue past the breakpoint.

What I see: the breakpoint has been removed.
What I expect to see: the breakpoint should still be in place.

Restarting Windows did not resolve the issue.

I cannot reproduce the issue on other websites.

I installed Canary. Could not reproduce the issue on Canary. Breakpoint worked as expected.
58.0.3025.0 (Official Build) canary (64-bit)

Deleted: screencap.gif 468 KB

	screencap.gif 468 KB View Download

Issue is still happening for me on Chrome  59.0.3047.4

Windows 10

1. "Goto File" in Dev tools, loading my JS file (say X.js) into tab 
2. Place break point(s) 
3. Perform operation which opens an iFrame which also loads X.js
4. break points "lost" as X.js is loaded
5. Dev tools shows two X.js tabs open 
6. Recreate break points
7. "Breakpoints" panel shows break points created in VM??? X.js

The original X.js is identical to X,js loaded  by iframe 
Dev tools "disable cache while dev tools is open" option is set 
(but toggling the options does not seems to make a difference) 

  

Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

#10 is fixed in current dev.
#11 is another issue and not fixed yet.

 Issue 697868  has been merged into this issue.