Closed Bug 1615320 Opened 4 years ago Closed 4 years ago

Firefox 73 shows only blank screen after upgrade or install on Windows 10

Categories

(Core :: mozglue, defect)

73 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1614885

People

(Reporter: allen_l_chesley, Unassigned)

Details

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

Steps to reproduce:

Was on 72, accepted upgrade to 73. Shows only blank screen.
Uninstalled 73, wiped out profile except for logins and bookmarks, and did new install of 72.0.2. That worked fine.
73 auto installed this morning and again only blank screen. Cannot see any web page, options, etc.

Actual results:

Cannot see any web page, options, etc.

Expected results:

See web page

See this Reddit thread for some suggestions:
https://old.reddit.com/r/firefox/comments/f2d5cu/nothing_will_load/

See also:
bug 1614885 - Firefox 73 no longer able to load content when launched in Win7 compatibility mode

(In reply to dickvl from comment #2)

See also:
bug 1614885 - Firefox 73 no longer able to load content when launched in Win7 compatibility mode

Not running in Compatibility Mode

(In reply to dickvl from comment #1)

See this Reddit thread for some suggestions:
https://old.reddit.com/r/firefox/comments/f2d5cu/nothing_will_load/

Exploit Protection is locked by the Site, but no settings changed between 72 and 73. 73 is broken.

I am seeing two processes for Firefox (parent + child)

could you test if the issue is fixed in today's nightly test builds?:
https://www.mozilla.org/firefox/all/#product-desktop-nightly

Firefox 75.0a1 works!

I also noticed that 73 seems to be having problems closing down. After I closed its window the two processes persisted, and I had to kill them by hand.

Also, how do I get my profile into he new version? No I cannot use a FF account - not allowed in my work environment.

thank you for the confirmation - although you're not running firefox in compat mode, you're apparently suffering from a problem of similar root cause, which is worked on in bug 1614885 - so i'll mark your report as a duplicate.

running nightly was only intended as a test at this stage, but you can expect to see an update for your firefox 73 sometime next week that should fix things there as well.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Component: Untriaged → mozglue
Product: Firefox → Core
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.