Closed
Bug 1619478
Opened 4 years ago
Closed 4 years ago
RDM doesn’t close between process switches
Categories
(DevTools :: Responsive Design Mode, defect, P1)
DevTools
Responsive Design Mode
Tracking
(firefox75 fixed)
RESOLVED
FIXED
Firefox 75
Tracking | Status | |
---|---|---|
firefox75 | --- | fixed |
People
(Reporter: mtigley, Assigned: mtigley)
References
(Blocks 1 open bug)
Details
(Whiteboard: fission-rdm-reserve)
Attachments
(1 file)
STR
- Make sure
devtools.target-switching.enabled
is false. - Open RDM and go to https://wiki.mozilla.org/Main_Page
- Navigate to about:robots
Expected
RDM should close due to a remoteness change from content -> parent processes.
Actual
RDM is still open. However, if you try closing RDM nothing will happen.
There's a race between the navigation from the content -> parent process and closing RDM as needed. So we need to make sure we're closing RDM before the navigation happens.
Assignee | ||
Comment 1•4 years ago
|
||
Target switching support involves actors being destroyed during process flips. However, when RDM is closed due to a remoteness change, we are still trying to call methods on an actor that has already been destroyed. We need to ensure this doesn't happen by only calling these methods in destroy
if RDM is being closed manually by the user.
Updated•4 years ago
|
Assignee: nobody → mtigley
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•4 years ago
|
||
Pushed by mtigley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7734215faecf Ensure that actor methods are not being called before a remoteness change r=bradwerth
Updated•4 years ago
|
Priority: P2 → P1
Whiteboard: fission-rdm-reserve
Comment 4•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox75:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 75
You need to log in
before you can comment on or make changes to this bug.
Description
•