1686454 - content processes seem to hang after MacOS goes into deep sleep

Status: RESOLVED DUPLICATE of bug 1682713

(Core :: Widget: Cocoa, defect, P2)

Description

[Neil Harris]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 11.1; rv:84.0) Gecko/20100101 Firefox/84.0

Steps to reproduce:

1. Browse the web with Firefox on Mac
2. Close the laptop
3. Come back later and open it again

Actual results:

All content in tabs freezes, but you can still close firefox using Command-Q. Firefox works fine when relaunched.

Expected results:

Firefox should not freeze after sleep.

Comment 1

[Neil Harris]

This is on MacOS Big Sur, version 11.1, on an 2020 M1 Macbook with 8G RAM.

This might possibly be related to Bug 1142957, but that has been marked as RESOLVED FIXED.

Comment 2

[BugBot [:suhaib / :marco]]

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

Comment 3

[Neil Harris]

Also, the exact version of Firefox is 84.0.2, 64-bit universal binary.

Comment 4

[Stephen A Pohl]

This seems identical to bug 1682713 which I just closed since it wasn't reproducible anymore. Could you confirm that this is still happening for you?

Comment 5

[Neil Harris]

(In reply to Stephen A Pohl [:spohl] from comment #4)

This seems identical to bug 1682713 which I just closed since it wasn't reproducible anymore. Could you confirm that this is still happening for you?

Although the effects seems very similar to me, I can't reproduce this by putting the machine to sleep with the "Sleep" menu command, or closing the lid and reopening it a few seconds later.

The problem I've observed seems to happen after the machine is unattended for quite some time, so perhaps this is a case of there being an even deeper sleep state.

Comment 6

[Rachel Hutchison]

I have this issue on the m1 mac mini with Firefox 84.0.2.

To reproduce, you will have to wait a minute or so for the machine to go to sleep. It wont happen if you simply close the lid and reopen it a few seconds later since the computer wont have actually gone to sleep yet.

I have a desktop machine with a backlit keyboard so it's pretty easy to tell when it's properly "asleep" since it will put the USB controller in a low power state which causes the backlight of the keyboard to turn off. At that point, after waking the computer Firefox will be totally unresponsive.

As a workaround until this is fixed you can force Firefox to run in x86 mode under Rosetta 2, and it will work as expected after waking from sleep.

Comment 7

[Neil Harris]

After quite some time unable to reproduce this for another time, I've had it happen again.

Here is where things start to get weird.

Clicking on any non-Firefox app window seems to start things working again, but only for a few clicks. Then it jams again. But the very next click on a non-Firefox app window then seems to delivers whatever the last pending click event was to Firefox, which reacts instantaneously, and the Firefox interface will the work again for a few clicks. And I could repeat this pattern over and over again.

As might be expected, quitting and re-launching Firefox returned everthing back to normal.

I will investigate further.

Comment 8

[Neil Harris]

I've just noticed this comment in another bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1682713#c24 , which seems to describe exactly what I described above in comment 7.

Comment 9

[Markus Stange [:mstange]]

We think bug 1682713 is now fixed on Nightly. Could you see if this bug still happens for you on Nightly, and report your findings in bug 1682713? Thanks!