Open
Bug 1709662
Opened 5 years ago
Updated 1 year ago
Use DocumentChannel to fix fission race conditions during process switches
Categories
(Core :: DOM: Navigation, defect, P3)
Core
DOM: Navigation
Tracking
()
NEW
| Fission Milestone | Future |
People
(Reporter: annyG, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged][domcore-bugbash-triaged])
[migrating notes from document "DocumentChannel remaining work"]
Use DocumentChannel to fix fission race conditions where the content process initiates a new load, while the existing load is process switching.
- Explained, along with a proposed solution in https://bugzilla.mozilla.org/show_bug.cgi?id=1580643#c12 .
- Maybe more theoretical than practical, maybe in tests?
- Could be possible for someone with slow network
- https://bugzilla.mozilla.org/show_bug.cgi?id=1581500#c41
|
||
Updated•5 years ago
|
Severity: -- → S4
Priority: -- → P2
Whiteboard: [necko-triaged]
|
||
Updated•5 years ago
|
Severity: S4 → S3
Fission Milestone: --- → Future
Component: Networking → DOM: Navigation
Priority: P2 → P3
|
||
Comment 1•1 year ago
|
||
I'm not sure if this is valid or not but maybe.
Whiteboard: [necko-triaged] → [necko-triaged][domcore-bugbash-triaged]
You need to log in
before you can comment on or make changes to this bug.
Description
•