Crash in [@ mozilla::net::LoadInfo::LoadInfo]
Categories
(Core :: Networking: HTTP, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox66 | --- | unaffected |
firefox67 | --- | unaffected |
firefox68 | + | fixed |
People
(Reporter: calixte, Assigned: mayhemer)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: crash, regression, topcrash, Whiteboard: [necko-triaged])
Crash Data
Attachments
(1 obsolete file)
This bug is for crash report bp-38cbb461-b358-463c-a76a-d7dde0190417.
Top 10 frames of crashing thread:
0 xul.dll mozilla::net::LoadInfo::LoadInfo netwerk/base/LoadInfo.cpp:290
1 xul.dll nsresult mozilla::net::nsIOService::NewChannelFromURIWithProxyFlagsInternal netwerk/base/nsIOService.cpp:907
2 xul.dll nsresult mozilla::net::nsIOService::NewChannelFromURIWithClientAndController netwerk/base/nsIOService.cpp:868
3 xul.dll NS_NewChannelInternal netwerk/base/nsNetUtil.cpp:370
4 xul.dll NS_NewChannel netwerk/base/nsNetUtil.cpp:313
5 xul.dll void mozilla::net::nsHttpChannel::PerformBackgroundCacheRevalidationNow netwerk/protocol/http/nsHttpChannel.cpp:10318
6 xul.dll nsresult mozilla::detail::RunnableMethodImpl<mozilla::net::nsHttpChannel*, void xpcom/threads/nsThreadUtils.h:1174
7 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1180
8 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
9 xul.dll void mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:88
There are 18 crashes (from 11 installations) in nightly 68 with buildid 20190416220148. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1536511.
[1] https://hg.mozilla.org/mozilla-central/rev?node=728aa342ad35
Comment 1•6 years ago
|
||
Crash report from macOS 10.11.6:
https://crash-stats.mozilla.org/report/index/a0983ea3-45db-4931-94cb-8b5cd0190417
Firefox crashes every time when trying to load https://www.ghacks.net. I wasn't able to reproduce the crash on other websites.
![]() |
Assignee | |
Comment 2•6 years ago
|
||
![]() |
Assignee | |
Updated•6 years ago
|
![]() |
Assignee | |
Comment 3•6 years ago
|
||
Comment 4•6 years ago
|
||
[Tracking Requested - why for this release]: #1 non-shutdown hang crash on Windows for the 3/17 Nightlies.
Comment 7•6 years ago
|
||
This is the #2 topcrash in the Windows nightly 20190418221600,
with 82 crashes from what looks like a significantly large number
of different installations.
Comment hidden (Intermittent Failures Robot) |
Comment 10•6 years ago
|
||
Boris, it'd be great to have this reviewed and fixed asap. Thanks!
Reporter | ||
Comment 11•6 years ago
|
||
The patch in bug 1536511 has been backed out.
Updated•6 years ago
|
Updated•6 years ago
|
![]() |
||
Comment 12•6 years ago
|
||
Sorry for the lag here; I was out most of last week...
Comment 13•6 years ago
•
|
||
(In reply to Calixte Denizet (:calixte) from comment #11)
The patch in bug 1536511 has been backed out.
How sure are we that this fixed the crash? I just hit this crash in the latest nightly [EDIT: turns out I wasn't running latest nightly, sorry for my confusion]
bp-d4e3019b-f1af-4afa-8221-9d4e20190423
bp-e1d1dc02-c3dc-4af2-847a-1d7d20190423
My STR:
(1) Visit https://imgur.com/gallery/dSYAaEb
(2) Save the page in Pocket (click the pocket icon at right edge of URLbar)
(3) Visit https://app.getpocket.com/ and click the new tile that you just created there ("tl;dw Game of Thrones Season 8, Episode 2 Recap - Album on Imgur")
Results:
crash [@ mozilla::net::LoadInfo::LoadInfo ], see bp-*** report links above.
Reporter | ||
Comment 14•6 years ago
|
||
:dholbert, the first report has buildid 20190418221600 and the second 20190417214729 and the first build with the backout is 20190422214919.
Fyi, if you've a look on the crash table on the top of this page, you can see that builds after 20190422214919 (included) don't have (at least for now) any crashes with this signature.
Comment 15•6 years ago
•
|
||
Ah, thank you & sorry for my confusion/false-alarm. Indeed, latest nightly doesn't crash after all, with my STR.
(In comment 13, I had only verified that I was on latest nightly [via Help|About] after I'd crashed twice -- and it seems I'd been initially running an old build, with an old-update staged to install, which is why I was still on an old version in my second crash. Each post-crash browser-restart got me a tick closer to the latest version.)
Comment 16•6 years ago
|
||
I just hit this on TB 67.0b3 x64: https://crash-stats.mozilla.com/report/index/6e673c7e-43cd-49dc-aa65-a92170190528#tab-bugzilla
Same issue?
Updated•4 years ago
|
Description
•