breakpoints in chrome don't work when i reload the html page

[dsn...@blueshiftinc.com]

when debugging haxe/javascript code, i set a breakpoint in the developer tools.  the first time i run the code, the breakpoint works.  when i reload the html page in the chrome, the breakpoint doesn't work.  the breakpoint is checked as "active".

if i click on the breakpoint to remove it and then click again to put the breakpoint back, the breakpoint works the next time i reload the html page.

is there a way to keep the breakpoint active when i reload the html page?

thanks,

doug

[Yury Semikhatsky]

The breakpoints should stay active on reload. The scenario you described sounds like a bug. Do the breakpoints restore on other pages after reload? If not can you provide a link to the page where we could reproduce it?

Yury

[Vsevolod Vlasov]

Could you please provide your browser version a well, this would be extremely helpful.thank you

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Vishnu Agarwal]

Not working for me as well 

OS : Mac 10.10.4 (14E46)

Chrome: Version 44.0.2403.155 (64-bit)

[Keith Miklas]

+1. Tremendously annoying. Debugging is hard enough!

Version 44.0.2403.125 (64-bit) Mac OSx v10.10.2

[Keith Miklas]

+1. Tremendously annoying. Difficult enough to debug, without my breakpoints disappearing on reload.

Chrome Version 44.0.2403.125 (64-bit) on Mac OSx Yosemite v10.10.2.

[Chad Baldwin]

Same here. Set a breakpoint in a Javascript file, refresh the page to hit the breakpoint, breakpoint disappears. Having to use Firefox to debug. I'm on Chrome 

Version 56.0.2924.87. Not surewhat the issue is. I've reset my settings and used CCleaner to clear out everything. Pretty positive it's a bug.

Sincerely,

Chad 

[PhistucK]

You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/af94a374-fff0-4e6c-b8bc-ffa7398d65a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.