Breakpoint still stopping after being deleted

Started having this problem since last updated, Webstorm 2017.2.4

Debug a NodeJS project (Node 0.10.48), where I place a break point before starting. Breakpoint is hit and all is fine. However, if I delete the breakpoint within the debug session, it keeps stopping at that point. I've opened the breakpoint window and force deleted everything. Still stops at my old line.

When I stop and restart the debug session, everything is fine.

10 comments
Comment actions Permalink

Can't recreate - breakpoint is cleared to me (tried with Node.js 6.10 and 8.5).

Can you check if upgrading Node.js version helps? 0.10 is no longer supported - see https://youtrack.jetbrains.com/issue/WEB-27150#comment=27-2202820

0
Comment actions Permalink

I've been dealing with this problem for years, across IntelliJ and Webstorm, and many computers.

I'm not sure why you can't reproduce it.

Unlike OP, this persists across multiple debug sessions (and I believe across Webstorm restarts)

0
Comment actions Permalink

>this persists across multiple debug sessions (and I believe across Webstorm restarts)

 

Removed breakpoints are hit after debug session/IDE restart? It's not about breakpoints clearing then. I can be a problem with sourcemaps, V8 engine limitation or a bug in IDE. In any case, a sample project + steps to repeat are required to track down the issue

0
Comment actions Permalink

I use PyCharm and I just had the same problem and figured out this:

The problem is not, that the debugger still stops, when Breakpoints are deleted.

The Problem is: Breakponts are not removed when you "click on the left border" (next to the row number). Although "the red spot" disappears, they are still in the list of "Python Line Breakpoints" and active, which is very confusing.

Hope you can reproduce and correct this behaviour ....

 

2
Comment actions Permalink

Good day,

I have the same issue. Worst, if I try to disable all break, running page fail in the browser and I need to stop and restart debugging session. Removing break points only hide the red dot. The break point is still happening.

I'm using PHPStorm 2020.3.2 with Docker 3.1.0 on macOS V10.14.6 with Safari 14.0.2

My PHP teacher had the same issue with the same environment.

Thank you.

0
Comment actions Permalink

Same issue here. PyCharm stops at removed breakpoints.

1
Comment actions Permalink

I've also been struggling with this for a while. Using Typescript, breakpoints often persist even after disabling them & restarting, it's making debugging my own app challenging to say the least.

When I set a breakpoint and tick "Disable until hitting the following breakpoint" option, the breakpoint works correctly the first time (only being triggered after the initial breakpoint is hit), however on subsequent runs, the breakpoint gets hit regardless of whether the initial breakpoint was hit, as though it's remembering it was hit during the previous debug session.

I'm using latest version of Webstorm, node v14.15.4. I will attempt to reproduce the problem in a sample project.

0
Comment actions Permalink

For me, the problem disappears after one of the updates of PHPStrom.

Now everything is fine.

0

Please sign in to leave a comment.