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)
DevTools
Debugger
Tracking
(firefox72 verified)
VERIFIED
FIXED
Firefox 72
Tracking | Status | |
---|---|---|
firefox72 | --- | verified |
People
(Reporter: Honza, Assigned: jlast)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
STRs:
- Load this page: http://janodvarko.cz/tests/debugger/watchpoints/
- Follow the test case #1
- When JS execution is paused in step #6 remove the Watchpoint
- Immediately create new one (the same)
- See the Browser Console, there is an exception:
uncaught exception: Protocol error (noSuchActor): No such actor for ID: server0.conn5.child1/obj36
Honza
Reporter | ||
Comment 1•5 years ago
|
||
@Jason, can you please look at this?
Honza
Flags: needinfo?(jlaster)
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → jlaster
Flags: needinfo?(jlaster)
Reporter | ||
Comment 2•5 years ago
|
||
Note that another scenario that is also causing this bug:
- Create a Watchpoint in an object (you can use the
person
from STRs comment #0) - Hover mouse over the
person
object in the source code - 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
Comment 3•5 years ago
|
||
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
Comment 6•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox72:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 72
Comment 7•5 years ago
|
||
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.
Description
•