Closed Bug 1689032 Opened 3 years ago Closed 3 years ago

Firefox 85.0 freezes on Windows, macOS 10.15.7 & linux on startup

Categories

(Core :: Networking: HTTP, defect, P1)

Firefox 85
Desktop
All
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox85 + fixed

People

(Reporter: mario_grgic, Unassigned)

References

Details

(Keywords: hang, regression, Whiteboard: [possible STR in comment 9])

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.2 Safari/605.1.15

Steps to reproduce:

Firefox updated today to version 85.0. After quitting Firefox normally, and starting later it now freezes every time. Activity monitor lists Firefox process as unresponsive.

This is happening on two different machines.

Actual results:

Firefox freezes. Process is marked as unresponsive.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Widget: Cocoa
Product: Firefox → Core

I have managed to fix this by making a backup of ~/Library/Application\ Support/Firefox, then starting Firefox with Option+Click which presents dialog to start in safe more or to rest Firefox (by the way starting in safe mode has no effect, Firefox is still unresponsive). I have reset Firefox. This creates new profile and copies some data from old profile. After quitting Firefox, I have deleted ~/Library/Application\ Support/Firefox and restored the backup of original Firefox directory with my old profile.

Firefox now works weirdly enough.

Without the original profile it will be difficult to debug this. You wouldn't happen to have kept a copy of it, would you?

Severity: -- → S3
Flags: needinfo?(mario_grgic)
Priority: -- → P3

I do actually have a backup of the original profile. I have even restored it as I mentioned above, but now Firefox works fine with original profile. I can only surmise that some caches must have gotten corrupt, since that is the only other data in ~/Library that Firefox maintains.

Flags: needinfo?(mario_grgic)

Interesting. I'd say we should close this bug for now but if this happens again, let us know and we can try to collect a process sample to debug further. I'll also make a note of this in case we get any other reports from users upgrading to version 85.0.

Same behavior here. Running version 85.0 on High Sierra 10.13.6
I have tried deleting and reinstalling app. Same hang behavior.
I will save Mario's workaround (below), but I'd rather the bug be fixed. I'll file my own bug report as well.

"I have managed to fix this by making a backup of ~/Library/Application\ Support/Firefox, then starting Firefox with Option+Click which presents dialog to start in safe more or to rest Firefox (by the way starting in safe mode has no effect, Firefox is still unresponsive). I have reset Firefox. This creates new profile and copies some data from old profile. After quitting Firefox, I have deleted ~/Library/Application\ Support/Firefox and restored the backup of original Firefox directory with my old profile."

(In reply to ellbee from comment #6)

Same behavior here. Running version 85.0 on High Sierra 10.13.6
I have tried deleting and reinstalling app. Same hang behavior.
I will save Mario's workaround (below), but I'd rather the bug be fixed.

Thanks. Since there are multiple reports of this issue, let's keep this bug open for further investigation. If you are able to reproduce this issue, please let us know so we can gather additional debug info.

I'll file my own bug report as well.

There is no need for new bugs. They will all be marked as duplicates of this bug report here since the same people will be investigating the issue.

My organization maintains the RECAP extension, and we've been getting reports of issues like this from our users. I'm not sure it's related to our extension or if we're just getting the blame (either way is bad), but I was able to reproduce this today.

STR:

  1. Install RECAP (no idea if needed, sorry)

  2. Upgrade FF

  3. Start FF

I looked at my monitor and it wasn't using CPU, which was weird, but eventually the OS dialog box came up to say that Firefox was frozen, and to ask if I wanted to kill FF or wait. I clicked wait a few times, then killed it.

Now when I restart FF, it's fine — I can't reproduce. It has something to do with the upgrade process, I think.

We've had a few users report this already. Seems like a bad bug. Could be extension-related, I don't know.

Happy to share profile details, but I didn't back it up before doing all this, sorry.

I guess I should also add that I'm on Linux using the version in Ubuntu's package manager, so this crosses OSes.

I went and downloaded FF84, installed RECAP, upgraded to 85, and then restarted FF, but wasn't able to reproduce this.

We've got a bug in our project over here: https://github.com/freelawproject/recap/issues/295. Somebody there seems to be able to reproduce it regularly, and reports that clearing the cache seems to fix it. This looks like a nasty one. Our extension is here:

https://free.law/recap/

We don't use any particularly unusual code at startup and haven't upgraded the extension in several months.

Reassigning to get some eyes with extension experience on this. See comment 9 and comment 12 in particular, and comment 10 indicating that this may be cross-platform.

Severity: S3 → S1
Component: Widget: Cocoa → Extension Compatibility
Priority: P3 → P1
Product: Core → Firefox
Summary: Firefox 85.0 freezes on macOS 10.15.7 on startup. → Firefox 85.0 freezes on macOS 10.15.7 & linux on startup

I don't have RECAP extension installed and I still ran into this problem. I also ran into same problem with Firefox Developer Edition 85 beta. There I only had uBlock Origin and React Developer Tools extensions.

With regular Firefox 85 I have uBlock Origin and SingleFile extensions.

It looks like clearing caches in ~/Library/Caches/Mozilla and ~/Library/Caches/Firefox fixes this problem.

(In reply to Mario Grgic from comment #14)

I don't have RECAP extension installed and I still ran into this problem. I also ran into same problem with Firefox Developer Edition 85 beta. There I only had uBlock Origin and React Developer Tools extensions.

With regular Firefox 85 I have uBlock Origin and SingleFile extensions.

It looks like clearing caches in ~/Library/Caches/Mozilla and ~/Library/Caches/Firefox fixes this problem.

I don't have RECAP, but I do have SingleFile extension along with many many others. But this fix worked for me too. Version 85 on MacOS 10.15.7

This...feels like it should be highly prioritized by now, given that we have a number of affected users and that it totally freezes FF.

I noticed that this bug also seems to occur on windows machines, some of our clients had this (plain profile, without any extensions) and two of my colleagues experienced it on their pcs (only ublock and noscript as extension).
After firefox starts, there is only a white screen and nothing happens.
As mentioned by others, I could fix it by renaming / deleting the corresponding cachefolder under AppData\Local\ under the profile directory of the user.

We seem to be running into an issue with our cache across all desktop platforms. Assigning to Firefox > General to get some eyes on this and redirect appropriately.

Component: Extension Compatibility → General
OS: Unspecified → All
Hardware: Unspecified → Desktop
Summary: Firefox 85.0 freezes on macOS 10.15.7 & linux on startup → Firefox 85.0 freezes on Windows, macOS 10.15.7 & linux on startup

I also experience this issue on Manjaro linux. Several other arch users reported that they have this issue, see https://bugs.archlinux.org/task/69457#comment196233. For me firefox hangs after every reboot since it was updated to 85.0. Restarting it in safe mode usually helps, but not always.

This started happening to me last week as well. Yesterday I download a fresh copy of Firefox 85 and copied into /Applications worked fine for the the day.

This morning? Instant hang on launching Firefox.

macOS 10.15.7

I can report similar behavior. In about 30 clients, the problem occurs in some since the update to version 85.0 (Windows X64). A reinstallation did not help here. If you rename the Firefox folder under %APPDATA%\Roaming\Mozilla\ Firefox starts again. But the solution is not in every case of permanent success. With the affected clients, it is often enough to close and reopen Firefox once and the problem occurs again?
Is there any hint to solve the problem permanently?

Lots of folks affected by this and really bad consequences as folks upgrade to 85. If people can't start Firefox because of this bug, they're going to just never use it again — they have no other choice.

I know bugzilla is very noisy, but I don't think this is getting the attention from the Mozilla folks it should be. This should be assigned to somebody by now...

This feels bad enough to warrant a 85.x point release. How do I wave the red flag more than I already am?

[Tracking Requested - why for this release]: A number of users are reporting that Firefox freezes on startup after upgrading to 85.

Somewhat similar symptoms described in bug 1690347.

See Also: → 1690347
See Also: → 1689809

Bug 1679933 (referenced in bug 1689809) talks about a startup hang after updating Firefox. There was a patch landed there on 86 but not 85.

See Also: → 1679933

The user experiencing the hang reported in bug 1679933 said they first saw it on Nightly on 11/20, which I think lines up with early Firefox 85.

Whiteboard: [possible STR in comment 9]

I tried twice to reproduce this by installing Firefox 84.0.2 on OSX, installing RECAP, then updating using About Firefox and restarting, but I was unable to reproduce a hang.

If somebody who can reproduce this on OSX can save and attach the crash information from the OSX crash dialog after using it to force quite Firefox, we can see if this might be the same issue as bug 1679933.

Attached file crash log
Here's the crash information from Firefox 85.0.1 on macOS Big Sur:

```

As a workaround I am able to open Firefox properly by clicking a link from an external application, like in an email or chat program. I did not need to modify my profile or any other setting.

I tried twice to reproduce this by installing Firefox 84.0.2 on OSX, installing RECAP, then updating using About Firefox and restarting, but I was unable to reproduce a hang.

This didn't work for me either. I think the RECAP/extension thing was a red herring and your extension community is just a group that happens to be engaged with users at a level where they hear about breakage. My guess is it's something nasty in the cache. Wasn't there a huge revamp done for that in 85?

Thanks for the crash information! It looks like release doesn't have detailed symbolized information. However, what is there does look like bug 1679933 to me.

The main thread is waiting on a mutex, which is the same as the other bug, though this is quite generic:
17 mozilla::detail::MutexImpl::lock() + 6 (libmozglue.dylib + 86454) [0x102fce1b6] 1-17
17 _pthread_mutex_firstfit_lock_slow + 211 (libsystem_pthread.dylib + 8636) [0x7fff205f01bc] 1-17
17 __psynch_mutexwait + 10 (libsystem_kernel.dylib + 12486) [0x7fff205c20c6] 1-17
*17 psynch_mtxcontinue + 0 (pthread + 9387) [0xffffff80034a34ab] (blocked by turnstile with priority 47 waiting for firefox (Firefox) [675] thread 0x26c0) 1-17

More compellingly, thread 0x26c0 is named "Cache2 I/O", which is also like bug 1679933. For the little part of the stack we can see, the cache thread is sitting in ConditionVariableImpl::wait(), which again is like bug 1679933.

Status: UNCONFIRMED → NEW
Component: General → Networking: HTTP
Depends on: 1679933
Ever confirmed: true
Keywords: hang, regression
Product: Firefox → Core
See Also: 1679933

Kershaw, could you please take a look at this bug and see if it looks like bug 1679933? I don't know if there's going to be another dot release but it seems like maybe we should uplift the patch there to 85. Thanks.

Flags: needinfo?(kershaw)
See Also: → 1684916

(In reply to Andrew McCreight [:mccr8] from comment #33)

Kershaw, could you please take a look at this bug and see if it looks like bug 1679933? I don't know if there's going to be another dot release but it seems like maybe we should uplift the patch there to 85. Thanks.

Yes, I agree it looks like bug 1679933. I'll request for uplifting.
Thanks.

Flags: needinfo?(kershaw)

:mario_grgic, since this bug is a regression, could you fill (if possible) the regressed_by field?
For more information, please visit auto_nag documentation.

Flags: needinfo?(mario_grgic)
Flags: needinfo?(mario_grgic)

I've been experiencing the same subjective problem -- Firefox 85 hanging on startup under both Win10 and Linux.

In my case, deleting favicons.sqlite from the active profile allows Firefox to start properly.

This may be a viable workaround for people who can't wait for a fix and don't want to wipe out their Firefox profiles every few days.

This should now be fixed in Firefox 85.0.2.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: