Removing and setting a set/get watchpoint doesn't work after resuming execution
Categories
(DevTools :: Debugger, defect, P1)
Tracking
(firefox72- wontfix, firefox73 fixed)
People
(Reporter: jarilvalenciano, Assigned: jarilvalenciano)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
|
(deleted),
text/x-phabricator-request
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.97 Safari/537.36
Steps to reproduce:
- Open http://janodvarko.cz/tests/debugger/watchpoints/
- Follow test case #1, and click the "Click Me!" button in step #2
- Set a watchpoint (set) on the age property of the person object
- Click Resume to pause on the watchpoint
- Click Resume again to finish pausing and resume execution
- Click on the "Click Me!" button again in test case #1, step #2
- Click on the age property's watchpoint marker to remove the watchpoint
- Try adding a set/get watchpoint
Actual results:
You should be able to put back the watchpoint after removing it.
Expected results:
Nothing happens.
Error:
JavaScript error: , line 0: uncaught exception: Protocol error (noSuchActor): No such actor for ID: server0.conn0.child1/obj78
|
||
Updated•5 years ago
|
Interesting to note that if you step over and then try to add a watchpoint, it does work.
|
||
Updated•5 years ago
|
|
||
Comment 3•5 years ago
|
||
I was able to reproduce on latest Nightly Version 73.0a1 Build ID 20191216214733 on Windows 10, macOS 10.15 and Ubuntu 18.04
Following the steps mentioned by the reporter, it is not possible to add a watchpoint after removing a previous one
|
|
||
Updated•5 years ago
|
|
||
Updated•5 years ago
|
|
|
||
Comment 4•5 years ago
|
||
Raising the priority here since it breaks the feature.
The patch is attached, close to landing?
Honza
Pushed by jlaster@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0cc5dce66033 Create WatchpointMap to keep track of objects with watchpoints r=jlast
|
||
Comment 7•5 years ago
|
||
| bugherder | ||
|
||
Updated•5 years ago
|
|
|
||
Comment 8•5 years ago
|
||
Verified - fixed on latest Nightly Version 73.0a1 Build ID 20191222215627 on Windows 10, Ubuntu 18-04 and macOS 10.15
|
|
||
Comment 9•5 years ago
|
||
[Tracking Requested - why for this release]: It's not clear to me whether this blocks shipping watchpoints in 72.
Can you request uplift to beta if you think this is necessary for the feature to launch, and if it's not too risky?
Jason, maybe you can help out with the uplift request?
|
||
Comment 12•5 years ago
|
||
As Jason is out on holidays and this is a larger change late in the cycle, I'll mark this as wontfix for 72.
|
|
||
Updated•5 years ago
|
|
|
||
Updated•4 years ago
|
|
|
||
Comment 13•4 years ago
|
||
I can confirm this issue is fixed. I verified on Windows 10, macOS 10.15 and Ubuntu 18.04. I'm updating the status flags since this issue is verified as fixed based on Comment 8.
Description
•