Closed Bug 1740202 Opened 3 years ago Closed 2 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)

defect

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

  1. Goto http://techno-barje.fr/fission/duplicated-url-scripts/
  2. Open the debugger
  3. 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
  4. Set breakpoint in on line 2
  5. 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

See Also: → 1740980
Assignee: nobody → hmanilla
Status: NEW → ASSIGNED
See Also: → 1755344
Depends on: 1755344
See Also: 1755344
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
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
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.

Attachment

General

Created:
Updated:
Size: