1873895 - Opening a new blank tab causes crash after applying Windows update KB5034129

Status: RESOLVED WORKSFORME

(Core :: DOM: Content Processes, defect, P2)

Description

[Chua Chee Wee]

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

Comment 1

[Chua Chee Wee]

This issue is seen on Firefox, Firefox Developer and Nightly (all latest version), on Windows Server 2022, with KB5034129 and KB5034272.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

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.

Comment 3

[Chua Chee Wee]

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:

Comment 4

[Chua Chee Wee]

Confirmed this is caused by KB5034129. After removal of KB5034129, these crashed tab issues are gone.

Comment 5

[Frederik Braun [:freddy]]

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?

Comment 6

[Chua Chee Wee]

(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

[Gian-Carlo Pascutto [:gcp]]

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.

Comment 8

[Chua Chee Wee]

Attachment: KB5034129 still being offered - 18 Jan 2024 10:19 AM UTC+0800

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

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:dao, could you have a look please?

For more information, please visit BugBot documentation.

Comment 10

[Jens Stutte [:jstutte]]

I read on support.microsoft.com that this update had an issue also with chrome based browsers and that this has been addressed by another update. Do we know if that helped also for Firefox?

For your reference:

After you install KB5034129, chromium-based internet browsers, such as Microsoft Edge, might not open correctly. Browsers affected by this issue might display a white screen and become unresponsive when you open them.
Devices that have browser specific Image File Execution Options (IFEO) might be affected by this issue. When an entry for Microsoft Edge (msedge.exe) or other chromium-based browsers is found in the Windows registry, the issue might occur. A registry entry can be created by developer tools or when certain debugging and diagnostic settings are in place for browsers.

Comment 11

[Chua Chee Wee]

(In reply to Jens Stutte [:jstutte] from comment #10)

I read on support.microsoft.com that this update had an issue also with chrome based browsers and that this has been addressed by another update. Do we know if that helped also for Firefox?

I am unable to say whether it does or not.
I have KB5034770 installed, and KB5034129 uninstalled, and KB5034129 is the one that caused the reported problem, not KB5034770.