Opening a new blank tab causes crash after applying Windows update KB5034129
Categories
(Core :: DOM: Content Processes, defect, P2)
Tracking
()
People
(Reporter: chuacw, Unassigned)
Details
Attachments
(1 file)
|
412.18 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0
Steps to reproduce:
New Tab
Actual results:
"Gah. Your tab just crashed.
We can help!
Choose Restore This Tab to reload the page."
Expected results:
no crash
| Reporter | ||
Comment 1•2 months ago
|
||
This issue is seen on Firefox, Firefox Developer and Nightly (all latest version), on Windows Server 2022, with KB5034129 and KB5034272.
Comment 2•2 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Reporter | ||
Comment 3•2 months ago
|
||
More details:
Faulting application name: firefox.exe, version: 121.0.1.8773, time stamp: 0x659c191e
Faulting module name: mozglue.dll, version: 121.0.1.8773, time stamp: 0x659c1904
Exception code: 0x80000003
Fault offset: 0x00000000000209cd
Faulting process id: 0x22b8
Faulting application start time: 0x01da43f658746b46
Faulting application path: C:\Program Files\Mozilla Firefox\firefox.exe
Faulting module path: C:\Program Files\Mozilla Firefox\mozglue.dll
Report Id: 4dad82e8-b78c-4b65-8d8c-46670fec1fd9
Faulting package full name:
Faulting package-relative application ID:
| Reporter | ||
Comment 4•2 months ago
|
||
Confirmed this is caused by KB5034129. After removal of KB5034129, these crashed tab issues are gone.
Comment 5•2 months ago
|
||
We'd like to explore if we can mitigate the crash or work around it, to make Firefox and KB5034129 no longer mutually exclusive. Can you maybe report a crash through the Firefox crash reporter and post the crash ID here?
| Reporter | ||
Comment 6•2 months ago
|
||
(In reply to Frederik Braun [:freddy] from comment #5)
We'd like to explore if we can mitigate the crash or work around it, to make Firefox and KB5034129 no longer mutually exclusive. Can you maybe report a crash through the Firefox crash reporter and post the crash ID here?
How would I do that? Do you have a special build for me, or special instructions?
The crash doesn't appear in the crash reporter, nor about:crashes.
The details reported in "More details" above came from Windows event viewer.
Comment 7•2 months ago
|
||
Re-opening. Would be good to have some idea about the amount of affected users, and whether this patch is still being offered to users.
| Reporter | ||
Comment 8•2 months ago
|
||
KB5034129 is still being offered as of 18 Jan 2024 10:19 AM UTC+0800 and still crashing Firefox, Firefox Nightly and Firefox Developer.
Comment 9•1 month ago
|
||
The severity field is not set for this bug.
:dao, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 month ago
|
Description
•