1615821 - Blank rendering panel even in Safe Mode since upgrading to Firefox 73

Status: RESOLVED DUPLICATE of bug 1614885

(Core :: mozglue, defect)

Description

[Adam Johnson]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.106 Safari/537.36

Steps to reproduce:

Start Firefox, with or without holding shift. I'm running Firefox 73.0.0.7342 on Windows 10 1809 (10.0.17763.1039)

Actual results:

browser controls are shown, but nothing shows in the rendering panel, not even about:config, even in Safe Mode. Windows event viewer Application log shows:

Application Error Event ID 1000
Faulting application name: firefox.exe, version: 73.0.0.7342, time stamp: 0x5e3dd850
Faulting module name: firefox.exe, version: 73.0.0.7342, time stamp: 0x5e3dd850
Exception code: 0xc0000005
Fault offset: 0x000000000001178f
Faulting process id: 0x40dc
Faulting application start time: 0x01d5e41269b0965a
Faulting application path: C:\Program Files\Mozilla Firefox\firefox.exe
Faulting module path: C:\Program Files\Mozilla Firefox\firefox.exe
Report Id: 959d3366-b3cd-43eb-8ce4-44f58a414b77
Faulting package full name:
Faulting package-relative application ID:

Expected results:

Start page should render, other pages should render, especially built-in ones like about:config

Comment 1

[Adam Johnson]

You may notice my Agent String is not very helpful for this but I couldn't use Firefox to report the bug.

Comment 2

[Gingerbread Man]

Can you reproduce this if you start with a brand new profile?
https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles

If yes, can you also reproduce it in the latest Nightly?
https://www.mozilla.org/firefox/nightly/all/

If yes, can you also reproduce it when doing the following?

1. Exit Firefox.
2. Copy the prefs.js file from your profile folder somewhere handy, like the desktop.
3. Open the original prefs.js in a text editor and search for browser.preferences.defaultPerformanceSettings.enabled and set it to false and dom.ipc.processCount and set that to 1. If those preference don't exist in the file, add these lines, then save and close the file:

user_pref("browser.preferences.defaultPerformanceSettings.enabled", false);
user_pref("dom.ipc.processCount", 1);

4. If the problem persists, exit Firefox again, then overwrite prefs.js with the backup copy from the desktop.

Comment 3

[[:philipp]]

can you check if downloading the update to firefox 73.0.1 that was released just now can address your issue?
https://www.mozilla.org/en-US/firefox/all/

Comment 4

[Adam Johnson]

Brand new profile still had the problem as well.
Didn't try Nightly, but 74.0b5 beta does NOT have the problem, so stopped looking at that point.
I did want to try turning off hardware acceleration, but didn't know where to go with about:config invisible, Looks like the prefs.js is the place, thanks, that may be helpful later.

Just tried running the Firefox Installer to get 73.0.1 - an application error popped up during the install and disappeared before I could read it, but 73.0.1 does render and seem to work ok. It did prompt to create a new profile, so I may go back to the beta line for now. Re-accepting all the network equipment self-signed certs again is a real pain, and doesn't seem to sync with my Firefox Sync account.

Looking in the Windows Event Viewer, there is an Application Error with the same Exception code as with 73.0 corresponding to the pop-up during install, different Fault offset though:

Faulting application name: firefox.exe, version: 73.0.1.7352, time stamp: 0x5e4abc33
Faulting module name: firefox.exe, version: 73.0.1.7352, time stamp: 0x5e4abc33
Exception code: 0xc0000005
Fault offset: 0x000000000001252f
Faulting process id: 0x3d50
Faulting application start time: 0x01d5e8b6d41de5e6
Faulting application path: C:\Program Files\Mozilla Firefox\firefox.exe
Faulting module path: C:\Program Files\Mozilla Firefox\firefox.exe
Report Id: b8488710-9760-42c6-abd3-887d373e10d3
Faulting package full name:
Faulting package-relative application ID:

Comment 5

[Adam Johnson]

74.0b6 also is fine in regards to the rendering panel

Comment 6

[[:philipp]]

thank you, it sounds like the same issue as bug 1614885 then which received a fix by now.