Crash in [@ shutdownhang | RtlAcquireSRWLockExclusive | mozilla::scache::StartupCache::GetBuffer]
Categories
(Core :: XPCOM, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | unaffected |
firefox79 | --- | unaffected |
firefox80 | + | verified |
firefox81 | + | fixed |
People
(Reporter: philipp, Assigned: alexical)
References
(Regression)
Details
(Keywords: crash, regression)
Crash Data
Attachments
(1 file)
[Tracking Requested - why for this release]:
This bug is for crash report bp-60f1d762-b1ef-4b9e-bacf-ca9510200803.
Top 10 frames of crashing thread:
0 ntdll.dll NtWaitForAlertByThreadId
1 ntdll.dll RtlAcquireSRWLockExclusive
2 xul.dll mozilla::scache::StartupCache::GetBuffer startupcache/StartupCache.cpp:840
3 xul.dll ReadCachedScript js/xpconnect/loader/mozJSLoaderUtils.cpp:25
4 xul.dll mozJSComponentLoader::ObjectForLocation js/xpconnect/loader/mozJSComponentLoader.cpp:758
5 xul.dll mozJSComponentLoader::Import js/xpconnect/loader/mozJSComponentLoader.cpp:1276
6 xul.dll mozilla::dom::module_getter::ModuleGetter dom/base/ChromeUtils.cpp:576
7 xul.dll InternalCall js/src/vm/Interpreter.cpp:640
8 xul.dll js::NativeGetExistingProperty js/src/vm/NativeObject.cpp:2325
9 xul.dll Interpret js/src/vm/Interpreter.cpp:3471
the volume of these shutdownhangs is jumping up noticably in firefox 80.0b - acoounting for ~2.75% of all browser crashes. this first started on nightly build 20200708094217 and therefore looks tied to the changes in bug 1627075.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
I don't think this will fully resolve the shutdown hangs associated
with this bug. The underlying problem is that writing the startup
cache during shutdown can take a long time. This seems like A Bad Thing,
and I have a mild leaning toward the thought that we shouldn't write the
startup cache at all during shutdown. However, I do think that trading
shutdown time regressions for startup time wins is probably good, so
I don't feel super comfortable making that change.
However, this change at least fixes the problem where we A) block the main
thread waiting for the write to finish, and B) are more likely to hit a
shutdown hang, since we concentrate all of the hang time in one phase,
rather than it being spread across the shutdown timeline. This is likely
the major change that the regressing bug introduced.
The unfortunate consequence is that if we try to GetBuffer during shutdown,
we will now read out of the omnijar. However, it should overall be better
since we'll be waiting on a (hopefully) small number of small reads rather
than a large write.
Updated•5 years ago
|
Comment 4•5 years ago
|
||
Backed out changeset 25e500b64866 for causing failures in TestStartupCache
Backout link: https://hg.mozilla.org/integration/autoland/rev/12ca712fdf780170f813353b4074d227f1b82ed5
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=312322271&repo=autoland&lineNumber=24240
Comment 6•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 7•5 years ago
|
||
The patch landed in nightly and beta is affected.
:dthayer, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 8•5 years ago
|
||
Trying to sort out what's going on in bug 1658732 before requesting uplift. That's a fairly strange regression to see from this change.
Comment 9•4 years ago
|
||
Bug 1627075 was backed out for 80.0rc2, so we'll hopefully see this go down in volume on Beta once that build starts rolling out.
Comment 10•4 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #9)
Bug 1627075 was backed out for 80.0rc2, so we'll hopefully see this go down in volume on Beta once that build starts rolling out.
No reports from 80.0rc2 - looks like the backout worked. Calling this fixed for Fx80 by bug 1656261.
Updated•4 years ago
|
Updated•4 years ago
|
Description
•