Closed Bug 1595716 Opened 5 years ago Closed 5 years ago

Protocol error (noSuchActor) exception when re-creating a Watchpoint

Categories

(DevTools :: Debugger, defect, P1)

defect

Tracking

(firefox72 verified)

VERIFIED FIXED
Firefox 72
Tracking Status
firefox72 --- verified

People

(Reporter: Honza, Assigned: jlast)

References

Details

Attachments

(1 file)

STRs:

  1. Load this page: http://janodvarko.cz/tests/debugger/watchpoints/
  2. Follow the test case #1
  3. When JS execution is paused in step #6 remove the Watchpoint
  4. Immediately create new one (the same)
  5. See the Browser Console, there is an exception: uncaught exception: Protocol error (noSuchActor): No such actor for ID: server0.conn5.child1/obj36

Honza

@Jason, can you please look at this?

Honza

Flags: needinfo?(jlaster)
Assignee: nobody → jlaster
Flags: needinfo?(jlaster)

Note that another scenario that is also causing this bug:

  1. Create a Watchpoint in an object (you can use the person from STRs comment #0)
  2. Hover mouse over the person object in the source code
  3. Click on the WP marker in the tooltip

You can also click in a tooltip within the Watch Expressions panel.
All rendered using the same component I guess.

Honza

Decision: Only show markers only in the Scopes panel, not anywhere else. Follow-up bug to add this as feature.

Pushed by jlaster@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/55cb09e11b06
Don't destroy the object actor after removing a watchpoint r=jlast
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 72

Verify-fixed on Beta Version 72.0b5 Build ID 20191210230245 on Windows 10, macOS 10.14 and Ubuntu 18.04

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: