Closed
Bug 1545105
Opened 5 years ago
Closed 5 years ago
Missing breakpoints should be removed
Categories
(DevTools :: Debugger, defect, P3)
DevTools
Debugger
Tracking
(Not tracked)
RESOLVED
INVALID
Firefox 68
People
(Reporter: jlast, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
The debugger naively sets pending breakpoints in the server assuming that if the breakpoint is no longer relevant there will be a chance to remove it via syncBreakpoint. At the moment though, we only remove breakpoints if there is no generated location AND the locations do not match. We might want to consider always removing the breakpoint if the generated location longer exists.
@@ -153,16 +179,17 @@ export function syncBreakpoint(
newLocation
if (!newGeneratedLocation) {
- // We couldn't find a new mapping for the breakpoint. If there is a source
- // mapping, remove any breakpoints for the generated location, as if the
- // breakpoint moved. If the old generated location still maps to an
- // original location then we don't want to add a breakpoint for it.
- if (location.sourceUrl != generatedLocation.sourceUrl) {
- dispatch(
- removeBreakpointAtGeneratedLocation(cx, sourceGeneratedLocation)
- );
- }
+ // if (location.sourceUrl != generatedLocation.sourceUrl) {
+ dispatch(
+ removeBreakpointAtGeneratedLocation(cx, sourceGeneratedLocation)
+ );
+ // }
return;
}
Reporter | ||
Updated•5 years ago
|
Priority: -- → P2
Reporter | ||
Comment 1•5 years ago
|
||
Brian, what do you think about this?
This bug is related to 1545103, which I just pushed to lando. So hopefully the zombie case is fixed, but I think we should still consider being more aggressive with syncing.
Flags: needinfo?(bhackett1024)
Reporter | ||
Comment 3•5 years ago
|
||
Reporter | ||
Updated•5 years ago
|
Target Milestone: --- → Firefox 68
Reporter | ||
Updated•5 years ago
|
Priority: P2 → P3
Updated•5 years ago
|
Whiteboard: [debugger-reserve]
Updated•5 years ago
|
Reporter | ||
Comment 4•5 years ago
|
||
we decided we do not want to do this
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Updated•5 years ago
|
Attachment #9059914 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•