Crash in [@ mozilla::net::nsHttpHandler::Init]
Categories
(Core :: Networking: HTTP, defect, P2)
Tracking
()
People
(Reporter: mccr8, Assigned: valentin)
Details
(Keywords: crash, Whiteboard: [necko-triaged][necko-priority-next])
Crash Data
Attachments
(3 files)
Crash report: https://crash-stats.mozilla.org/report/index/c2a9a029-6c85-45a8-a622-8af550230621
MOZ_CRASH Reason: MOZ_DIAGNOSTIC_ASSERT(false) (Try to init HttpHandler after shutdown)
Top 10 frames of crashing thread:
0 xul.dll mozilla::net::nsHttpHandler::Init netwerk/protocol/http/nsHttpHandler.cpp:314
0 xul.dll mozilla::net::nsHttpHandler::GetInstance netwerk/protocol/http/nsHttpHandler.cpp:204
1 xul.dll mozCreateComponent startupcache/StartupCacheInfo.cpp:49
1 xul.dll mozilla::xpcom::CreateInstanceImpl xpcom/components/StaticComponents.cpp:11299
2 xul.dll mozilla::xpcom::StaticModule::CreateInstance const xpcom/components/StaticComponents.cpp:13375
2 xul.dll xpcom/components/nsComponentManager.cpp:184
2 xul.dll nsComponentManagerImpl::GetServiceLocked xpcom/components/nsComponentManager.cpp:971
3 xul.dll nsComponentManagerImpl::GetServiceByContractID xpcom/components/nsComponentManager.cpp:1160
3 xul.dll CallGetService xpcom/components/nsComponentManagerUtils.cpp:61
3 xul.dll nsGetServiceByContractID::operator const xpcom/components/nsComponentManagerUtils.cpp:240
Updated•3 years ago
|
Updated•3 years ago
|
Comment 1•3 years ago
|
||
I think we can log the JS location to find out what code tries to create channel during shutdown.
Comment 2•3 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 20 desktop browser crashes on beta
:edgul, could you consider increasing the severity of this top-crash bug?
For more information, please visit BugBot documentation.
Kershaw, thoughts on raising severity?
Comment 4•3 years ago
|
||
(In reply to Ed Guloien [:edgul] from comment #3)
Kershaw, thoughts on raising severity?
This crash happens during shutdown, so a user might not notice this.
I think we can leave this as S3.
| Reporter | ||
Comment 5•3 years ago
|
||
It is also a diagnostic assert, so it won't affect release users.
Comment 6•3 years ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit BugBot documentation.
Comment 7•3 years ago
|
||
Sorry for removing the keyword earlier but there is a recent change in the ranking, so the bug is again linked to a topcrash signature, which matches the following criterion:
- Top 20 desktop browser crashes on beta
For more information, please visit BugBot documentation.
Comment 8•3 years ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 9•2 years ago
|
||
It seems a bunch of these are happening through dom/xhr/XMLHttpRequestMainThread.cpp:2539 calling NS_NewChannel after shutdown.
We should add a check to NS_NewChannel and return error during shutdown.
| Assignee | ||
Comment 10•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
Comment 13•2 years ago
|
||
There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:valentin, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 14•2 years ago
|
||
| Assignee | ||
Comment 15•2 years ago
|
||
Comment 16•2 years ago
|
||
Comment 17•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/5526248c0be2
https://hg.mozilla.org/mozilla-central/rev/22d329ce0ffc
Updated•2 years ago
|
Comment 18•2 years ago
|
||
The patch landed in nightly and beta is affected.
:valentin, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox128towontfix.
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Updated•2 years ago
|
Description
•