Crash in [@ AsyncShutdownTimeout | profile-change-teardown | Extension shutdown: formautofill@mozilla.org ,Extension shutdown: pictureinpicture@mozilla.org ,Extension shutdown: screenshots@mozilla.org ,Extension shutdown: webcompat@mozilla.org ]
Categories
(Toolkit :: Add-ons Manager, defect, P1)
Tracking
()
People
(Reporter: vlucaci, Unassigned)
References
Details
(Keywords: crash, regression)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/17c2cde0-3828-4e0a-b6c1-3c0f20211026
MOZ_CRASH Reason: MOZ_CRASH()
Top 10 frames of crashing thread:
0 mozglue.dll mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33
1 xul.dll NS_DebugBreak xpcom/base/nsDebugImpl.cpp:435
2 xul.dll nsDebugImpl::Abort xpcom/base/nsDebugImpl.cpp:134
3 xul.dll XPTC__InvokebyIndex
4 @0x239fb46a21f
5 xul.dll _tailMerge_d3dcompiler_47.dll
6 xul.dll static XPCWrappedNative::CallMethod js/xpconnect/src/XPCWrappedNative.cpp:1130
7 xul.dll XPC_WN_CallMethod js/xpconnect/src/XPCWrappedNativeJSOps.cpp:921
8 xul.dll js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:488
9 xul.dll Interpret js/src/vm/Interpreter.cpp:3255
Affected versions*
- 93.0
Affected platforms
- Windows 11
Preconditions
- Firefox is installed from official https://www.mozilla.org/en-US/firefox/new/
- Have a dirty profile with bookmarked pages , saved logins, custom theme, pinned tabs, addons (Ublock Origins and Tabby Cat) and close the browser normally.(via X button)
- Had Microsoft Office Word 2019 , Skype running in background.
Steps to reproduce
- Attempt to launch FF.
Expected result
- Firefox is launched without any issues.
Actual result
- A broken FF session is opened, no webpages are loading, tabs names are not displayed, even internal pages (about:crashes for example) are unreachable.
- Closing FF leaves the process running in Task Manager, you have to manually end the task for a new session to be launched.
- After the crash is encountered, vcruntime140.Dll Is Missing error is received on each launch.
Suggested Severity
- Seeing as how FF is unusable after this crash is encountered, as well as receiving the vcruntime140.dll error, I would consider this issue an S1. (even though I only managed to reproduce this issue on this specific platform)
Regression range
- It could potentially be the same regression range from the 1464938 : https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=3eccd139667d491ca259e8ff96f740ecfa36a781&tochange=db78be8dbc1c81844eb7d35c1a3073078eb5d923
Additional notes
- This error is received only in FF, and no other executable.
- Only reinstalling Microsoft C++ 2015-2019 and FF rendered the vcruntime140dll error to stop being received.
Comment 2•2 years ago
|
||
(haven't looked into this yet)
Is this an one-off crash, or consistently reproducible?
Reporter | ||
Comment 3•2 years ago
|
||
I only managed to reproduce this crash just once.
Comment 4•2 years ago
|
||
Is this accurately flagged as S1 if we cannot repro?
Comment 5•2 years ago
|
||
(In reply to Vlad Lucaci, QA (:vlucaci) from comment #0)
Crash report: https://crash-stats.mozilla.org/report/index/17c2cde0-3828-4e0a-b6c1-3c0f20211026
A fragment of AsyncShutdownTimeout is as follows (the rest of the conditions have a similar stack trace).
{
"phase": "profile-change-teardown",
"conditions": [
{
"name": "Extension shutdown: webcompat@mozilla.org",
"state": {
"state": "Startup: Run manifest, asyncEmitManifestEntry(\"background\")"
},
"filename": "resource://gre/modules/addons/XPIProvider.jsm",
"lineNumber": 2620,
"stack": [
"resource://gre/modules/addons/XPIProvider.jsm:startup/<:2620",
"resource://gre/modules/AsyncShutdown.jsm:observe:575",
"resource://gre/modules/ResetProfile.jsm:openConfirmationDialog:100"
]
},
...
From the above stack trace, it seems that you've tried to reset the browser profile.
- A broken FF session is opened, no webpages are loading, tabs names are not displayed, even internal pages (about:crashes for example) are unreachable.
- Closing FF leaves the process running in Task Manager, you have to manually end the task for a new session to be launched.
Looks like the installation or environment has become corrupted to the extent that it's not salvageable.
It could be that the reported error/crash here is not the cause, but a symptom of the issue.
It's unlikely caused by the extension process failing to start (e.g. due to missing DLLs), because that scenario has been addressed by the fix of bug 1501375.
- After the crash is encountered, vcruntime140.Dll Is Missing error is received on each launch.
According to the crash report, the library is present ("VCRUNTIME140.dll 14.16.27012.6 B0FA7FB92B5F498590C4FAC82CF5FBA01").
- This error is received only in FF, and no other executable.
- Only reinstalling Microsoft C++ 2015-2019 and FF rendered the vcruntime140dll error to stop being received.
Did the re-installation of Firefox fix the issue, or was it necessary to re-install the MSVC runtime libraries?
From the information provided so far, it seems like the root cause of the observation is a corrupted environment/installation. Because of that, I'll close the bug.
Comment hidden (spam) |
Description
•