Closed
Bug 1740202
Opened 3 years ago
Closed 3 years ago
Add test for breakpoint set in one thread context gets hit in the other (with no visible breakpoint)
Categories
(DevTools :: Debugger, defect, P2)
DevTools
Debugger
Tracking
(firefox100 fixed)
RESOLVED
FIXED
100 Branch
Tracking | Status | |
---|---|---|
firefox100 | --- | fixed |
People
(Reporter: bomsy, Assigned: bomsy)
References
(Blocks 2 open bugs)
Details
(Whiteboard: dt-fission-future)
Attachments
(1 file)
This bug is for adding a test for this scenario. See fix would be done in Bug 1740980
STR
- Goto http://techno-barje.fr/fission/duplicated-url-scripts/
- Open the debugger
- In the source tree, select file
duplicate-distinct-thread.js
file in iframe ie.http://78.225.48.12:2323/fission/duplicate-scripts.html
->techno-barje.fr
->fission/duplicated-url-scripts
->duplicate-distinct-thread.js
- Set breakpoint in on line 2
- Click on the page on the top document
AR
The breakpoint is hit in Main Thread
-> techno-barje.fr
->fission/duplicated-url-scripts
-> duplicate-distinct-thread.js
which no breakpoint was set and is showing.
ER
The breakpoint should not hit in the file in the Main Thread
Updated•3 years ago
|
Blocks: dbg-breakpoint
Assignee | ||
Updated•3 years ago
|
Blocks: dbg-zombie-breakpoint
Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Assignee: nobody → hmanilla
Status: NEW → ASSIGNED
Assignee | ||
Updated•3 years ago
|
Pushed by hmanilla@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4a517e9d5aa7
[devtools] Test for breakpoints in same files in different targets r=ochameau
Comment 3•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox100:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
Assignee | ||
Updated•3 years ago
|
Summary: Breakpoint set in one thread context gets hit in the other (with not visible breakpoint) → Add test for breakpoint set in one thread context gets hit in the other (with no visible breakpoint)
You need to log in
before you can comment on or make changes to this bug.
Description
•