Closed Bug 2007232 Opened 11 months ago Closed 10 months ago

Firefox freezes after waking from sleep if external display was disconnected while asleep (macOS 26)

Categories

(Core :: Widget: Cocoa, defect)

Firefox 146
defect

Tracking

()

RESOLVED DUPLICATE of bug 1985140

People

(Reporter: mohit.ritanil, Unassigned)

Details

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

Steps to reproduce:

  1. Connect MacBook to external display via DisplayPort → USB-C
  2. Open Firefox 146.0 (aarch64) with windows/tabs open
  3. Allow MacBook to go to sleep (lid closed or automatic sleep)
  4. Disconnect external display while MacBook remains asleep
  5. Wake MacBook

Actual results:

Firefox becomes completely unresponsive:

  • Cannot click anywhere in the window
  • Cannot interact with tabs, address bar, or any UI elements
  • Can only resize the window
  • Firefox does not recover even after waiting several minutes
  • Can quit normally via File → Quit, but no other interaction is possible

This happens consistently every time the above steps are followed.

Additional notes:

  • This does NOT occur if the MacBook is woken up first (while still connected) and then the display is disconnected
  • The issue is specific to disconnecting the display while the MacBook is asleep

Expected results:

irefox should remain responsive after waking from sleep and handle the display disconnection gracefully, allowing normal interaction with all UI elements.

Summary: macos 26 external monitor wake freeze hang → Firefox freezes after waking from sleep if external display was disconnected while asleep (macOS 26)

This is not related to circular bookmark bug.

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Cocoa' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

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

@mohit.ritanil, thanks for the report. This sounds like bug 1985140 which we've recently fixed in Firefox 147 Beta. Assuming no problems are uncovered, this is expected to start shipping to users in Firefox 147 on January 13.

Status: UNCONFIRMED → RESOLVED
Closed: 10 months ago
Duplicate of bug: 1985140
Resolution: --- → DUPLICATE
Severity: -- → S2
You need to log in before you can comment on or make changes to this bug.