Cant disable breakpoints

[Jakub T]

Hello,

Im unable to disable breakpoints in developer tools. I have Deactivated breakpoints using CTRL+F8 so the icon is blue, but whenever javascript gets to debugger command the breakpoint is fired anyway and script stops. This only happens to me on one machine so I guess it some setting that breaks it. Can you please help me? I havent found anything relative on this forum, only relative topic was here https://productforums.google.com/forum/#!topic/chrome/oJH9mBIhYys but it wasnt resolved and it was even closed .

my current version of google chrome is Version 48.0.2564.103 m (64-bit) .

Thank you !

[Ken Kahn]

This occasionally happens to me as well. I'm not sure but I think in my case it was because I had multiple instance of Chrome Development Tools open and set a breakpoint in one and tried to remove it another. The few times it has happened to me it stops breaking on the removed breakpoint after an hour or two.

[Tom Granerød]

I have the same issue on version 48.0.2564.97 (64-bit) on OS X. A colleague of mine also has the same issue. A tad bit annoying.

[Andrey Lushnikov]

Hi guys,

I've filed a bug on your behalf: https://code.google.com/p/chromium/issues/detail?id=585870

Andrey

--
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/550aeaf5-4863-4b01-9402-615b72cf9fc0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[parvathy havaji]

I faced the same issue. The breakpoint was present in a minified script file and was not able to disable or remove it.

But clicking print option opens a formatted minified file. And was able to remove the breakpoint from it.

[Kim Carter]

Still not fixed in 67.

[PhistucK]

67 is a bit old, try the latest - 69.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chrome DevTools" 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/8bec126c-44f9-4eb7-99f1-0bc2b58f8f19%40googlegroups.com.

[tomaz....@timetac.com]

Still same issue in 71, can't remove in the breakpoints panel.

On Sunday, 16 September 2018 07:47:57 UTC+2, PhistucK wrote:

67 is a bit old, try the latest - 69.

☆PhistucK

On Sun, Sep 16, 2018 at 8:46 AM Kim Carter <binar...@gmail.com> wrote:

Still not fixed in 67.

On Tuesday, August 28, 2018 at 10:26:26 PM UTC+12, parvathy havaji wrote:

I faced the same issue. The breakpoint was present in a minified script file and was not able to disable or remove it.

But clicking print option opens a formatted minified file. And was able to remove the breakpoint from it.

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

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

[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

On Tue, Dec 4, 2018 at 4:49 PM <tomaz....@timetac.com> wrote:

Still same issue in 71, can't remove in the breakpoints panel.

On Sunday, 16 September 2018 07:47:57 UTC+2, PhistucK wrote:

67 is a bit old, try the latest - 69.

☆PhistucK

On Sun, Sep 16, 2018 at 8:46 AM Kim Carter <binar...@gmail.com> wrote:

Still not fixed in 67.

On Tuesday, August 28, 2018 at 10:26:26 PM UTC+12, parvathy havaji wrote:

I faced the same issue. The breakpoint was present in a minified script file and was not able to disable or remove it.

But clicking print option opens a formatted minified file. And was able to remove the breakpoint from it.

--
You received this message because you are subscribed to the Google Groups "Chrome DevTools" 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/8bec126c-44f9-4eb7-99f1-0bc2b58f8f19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "Chrome DevTools" 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/4ef2f473-64b3-46e8-963b-f0cb614ef9b7%40googlegroups.com.

[Jake Bellacera]

This happens to me on occasion as well. I'm not sure why, but it seems like Chrome's development tools will occasionally re-map a breakpoint onto an extension's JS file, and when the breakpoint is activated, my development tools tab locks up and I am unable to disable the breakpoint or resume script execution, which makes the tab effectively frozen.

Here's my suggested solution:

1. Open a new tab so that it is pointing to the default Chrome start page or a blank page
2. Open up the development tools
3. Navigate to the sources tab within the development tools pane
4. Disable the problematic breakpoint