Closed
Bug 1802910
Opened 2 years ago
Closed 2 years ago
We should not try to create nsHttpHandler during shutdown
Categories
(Core :: Networking: HTTP, enhancement, P3)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
111 Branch
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: kershaw, Assigned: kershaw)
References
Details
(Whiteboard: [necko-triaged][necko-priority-review])
Attachments
(1 file)
Based on the discussion on Slack with Jens, we should not try to create nsHttpHandler if we are InOrBeyond(AppShutdownNetTeardown)
to avoid late instantiation.
Comment 1•2 years ago
|
||
This might not be an issue after https://phabricator.services.mozilla.com/D162804 lands.
Comment 2•2 years ago
|
||
I think we can just add a diagnostic_assert to the nsHttpHandler constructor.
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → kershaw
Assignee | ||
Updated•2 years ago
|
Flags: needinfo?(kershaw)
Assignee | ||
Updated•2 years ago
|
Flags: needinfo?(kershaw)
Assignee | ||
Comment 3•2 years ago
|
||
Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/69a1d2fc5e76
Avoid creating http handler after shutdown, r=necko-reviewers,valentin
Comment 5•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox111:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•