Conditional breakpoints are never hit

[Mark Macdonald]

I've been having a problem for several weeks where the Chrome debugger never stops at conditional breakpoints, even with trivial conditions like true or 1. The debugger statement works, and non-conditional breakpoints work, but as soon as a condition is set, the breakpoint get skipped.

In sequential code, I can set a breakpoint with condition true on line N, and a breakpoint with no condition on line N+1. Execution skips past line N and stops at N+1.

I have tried various debugging steps, to no avail:

• Incognito Mode
• Switching channels between Beta (37.0.2017.2 beta-m) and Canary (37.0.2058.2)
• Debugging different websites (eg. localhost, twitter.com, etc)
• Creating a new profile by renaming %LOCALAPPDATA%\Google\Chrome\User Data\Default
• Disabling the computer's firewall (Symantec Endpoint Protection)

Has anyone ever observed something like this? I can't figure it out. The problem only occurs on 1 of my computers, but (of course) it's the development machine I need to use for work.

Thanks
Mark

[Vsevolod Vlasov]

Please file a bug on crbug.com/new

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/706d7d10-8836-4b8c-a17c-e68be94f9cc1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Vsevolod Vlasov]

Nevermind, I filed it myself: https://code.google.com/p/chromium/issues/detail?id=386969