Windows Crash in [@AsyncShutdownTimeout | profile-change-teardown | Extension shutdown: addons-search-detection@mozilla.com ,Extension shutdown: formautofill@mozilla.org ,Extension shutdown: pictureinpicture@mozilla.org ,Extension shutdown:
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox97 | --- | wontfix |
| firefox98 | --- | wontfix |
| firefox99 | --- | wontfix |
People
(Reporter: aryx, Unassigned)
References
Details
(Keywords: crash, regression)
Crash Data
Top crash #8 for Firefox 97.0, 211 crash reports from 207 installations, all on Windows
Crash report: https://crash-stats.mozilla.org/report/index/d129054d-a3e6-4a39-a877-2d3770220210
MOZ_CRASH Reason: [Parent 17804, Main Thread] ###!!! ABORT: file resource://gre/modules/addons/XPIProvider.jsm:2606
Top 10 frames of crashing thread:
0 xul.dll NS_DebugBreak xpcom/base/nsDebugImpl.cpp:433
1 xul.dll nsDebugImpl::Abort xpcom/base/nsDebugImpl.cpp:132
2 xul.dll XPTC__InvokebyIndex
3 None @0x0000023c38df44bf
4 xul.dll std::_Func_impl_no_alloc<`lambda at /builds/worker/checkouts/gecko/dom/media/ipc/RemoteDecoderChild.cpp:121:22', mozilla::ShmemBuffer, unsigned long long>::_Do_call
5 None @0xfff8800000000a2d
6 xul.dll _tailMerge_d3dcompiler_47.dll
7 xul.dll _tailMerge_d3dcompiler_47.dll
8 xul.dll _tailMerge_d3dcompiler_47.dll
9 xul.dll XPCWrappedNativeScope::UpdateWeakPointersAfterGC js/xpconnect/src/XPCWrappedNativeScope.cpp:273
|
Reporter | |
Comment 1•4 years ago
|
||
Bug 1738002 mentions this is from corrupted environments/installations.
|
||
Comment 2•4 years ago
|
||
The increase looks correlated to the launch of Fx95. I don't see any new system addons between 94 and 95, though the web compat reporter addon did increase in version. I'm wondering if this was a signature change. Any thoughts on this, Rob?
|
||
Comment 3•4 years ago
|
||
This specific signature started to appear more frequently on 7 dec 2021 (Fx95 release), and I believe that it's primarily a signature change. The addons-search-detection add-on was initially shipped via Balrog (since August 2021) and moved into the tree since the 95 branch in bug 1735721 (on release since 7 dec 2021), while the reset-search-defaults add-on stopped being distributed (bug 1718193). I've edited the signature field of this bug to include all addons-search-detection add-ons.
I looked up all crash reports related to the addons-search-detection system add-on. This add-on was initially shipped via Balrog (since August 2021), and the current version is in the tree since bug 1735721, Fx95 (on release since December 2021).
The Balrog version had a lower version and was installed in the profile, whereas the in-tree version is packaged with the browser and installed and enabled after startup, when all windows have been restored.
There are 18519 crash reports involving this add-on in the past 6 months, shown below. I don't see a spike specific to 95; if anything the volume went slightly down.
Summarized (data from 15 aug - 15 feb; *= incomplete data):
| versions (+release date) | reports | % of 18519 | notes |
|---|---|---|---|
| 90.0, 90.0.1, 90.0.2 (13 jul) | 555* | 3.00 % | incomplete; initial reports have expired |
| 91.0, 91.0.1, 91.0.2 (10 aug) | 2820* | 15.23 % | incomplete; some initial reports have expired (5 days) |
| 92.0, 92.0.1 (7 sep) | 3860 | 20.84 % | |
| 93.0 (5 oct) | 1927 | 10.41 % | |
| 94.0, 94.0.1, 94.0.2 (2 nov) | 3107 | 16.78 % | |
| 95.0, 95.0.1, 95.0.2 (7 dec) | 2580 | 13.93 % | First version with add-on in tree instead of via balrog - bug 1735721 |
| 96.0, 96.0.1, 96.0.2, 96.0.3 (11 jan) | 1299 | 7.01 % | |
| 97.0 (8 feb) | 873* | 4.71 % | incomplete; current cycle hasn't ended yet |
| other | 1498 | 8.09 % |
To get insight on the impact of expired crash reports on the reported numbers, I summarized crash reports from the past 3 months (15 nov - 15 feb) for comparison.
| versions (+release date) | reports | % of 8218 | notes |
|---|---|---|---|
| 90.0.2 | 75 | 0.91 % | incomplete; initial reports outside date range |
| 91.0, 91.0.1, 91.0.2 | 171 | 2.08 % | incomplete; initial reports outside date range |
| 92.0, 92.0.1 | 265 | 3.22 % | incomplete; initial reports outside date range |
| 93.0 | 231 | 2.81 % | incomplete; initial reports outside date range |
| 94.0, 94.0.1, 94.0.2 | 2046 | 24.90 % | incomplete; halfway the cycle; 1061 of 3107 reports outside date range |
| 95.0, 95.0.1, 95.0.2 | 2580 | 31.39 % | |
| 96.0, 96.0.1, 96.0.2, 96.0.3 | 1299 | 15.81 % | |
| 97.0 | 873 | 10.62 % | incomplete; current cycle hasn't ended yet |
| other | 678 | 8.25 % |
broken down by individual versions (15 nov - 15 feb):
| version | reports | % of 18519 |
|---|---|---|
| 92.0 | 2367 | 12.78 % |
| 93.0 | 1927 | 10.41 % |
| 94.0.1 | 1572 | 8.49 % |
| 92.0.1 | 1493 | 8.06 % |
| 91.0.2 | 1415 | 7.64 % |
| 95.0.2 | 1196 | 6.46 % |
| 94.0.2 | 1164 | 6.29 % |
| 95.0 | 1085 | 5.86 % |
| 97.0 | 873* | 4.71 % |
| 91.0.1 | 843* | 4.55 % |
| 91.0 | 562* | 3.03 % |
| 90.0.2 | 495* | 2.67 % |
| 96.0.3 | 454 | 2.45 % |
| 94.0 | 371 | 2.00 % |
| 96.0.2 | 364 | 1.97 % |
| 96.0.1 | 312 | 1.68 % |
| 95.0.1 | 299 | 1.61 % |
| 96.0 | 169 | 0.91 % |
| other | 1558 | 8.41 % |
|
|
||
Comment 4•4 years ago
|
||
With the updated signature set, the "Fx 95" spike is no longer apparent. There is a recent spike on 9 feb (97 release), but that seems to happen with every release (see bug 1464938's graph).
The spike happens because around the time of a release, many people restart Firefox, which could trigger this bug.
|
|
||
Updated•4 years ago
|
|
||
Updated•4 years ago
|
Description
•