Closed Bug 1782522 Opened 2 years ago Closed 2 years ago

Firefox crashes after unplugging from dock with one monitor

Categories

(Core :: Widget: Gtk, defect, P3)

Product:
Core
Component:
Widget: Gtk
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1793922

People

(Reporter: manuel, Unassigned)

References

(Blocks 1 open bug)

Details

Crash Data

+++ This bug was initially created as a clone of Bug #1762867 +++

STR:

  1. having firefox running
  2. open laptop lid (+1 montor)
  3. unplug usb-c hub (-1 monitor)
  4. firefox crashes

System: Firefox 103.0 (64-bit), Gnome 42.3 on Wayland, Arch Linux
https://crash-stats.mozilla.org/report/index/791812db-df8a-4673-a7cb-277600220801#tab-details

Can you repro with our binaries as well ?

Flags: needinfo?(mbucher)

Yes, I've downloaded and installed the version now, had both versions open, and both crashed at the same time:

Flags: needinfo?(mbucher)

I can record a rr session and upload to pernosco if that would be helpful.

I guess it could help, but it's not code I own and only fixed it last time because it was blocking me. Someone else from gfx might need to have a look. Might be good to also check if it was already broken after bug 1762867 landed, of if it's a regression, so mozregression it?

Sadly I couldn't reproduce with rr yet. And it isn't reliable enough to do mozregression with :/.

This is the new crash signature w/ inline information and I think it makes the bug more readable. It seems like the mScreenList array and the mMonitors one are not updated in sync, so the call to GetMonitorForWindow() here returns a screen that's already been removed from the list.

Crash Signature: [@ mozilla::detail::InvalidArrayIndex_CRASH | mozilla::widget::ScreenGetterWayland::GetScreenForWindow] → [@ mozilla::detail::InvalidArrayIndex_CRASH | mozilla::widget::ScreenGetterWayland::GetScreenForWindow] [@ mozilla::detail::InvalidArrayIndex_CRASH | nsTArray_Impl<T>::ElementAt | nsTArray_Impl<T>::operator[] | mozilla::widget::ScreenGetterWayland::GetSc…

I've hit this crash while attempting to reproduce this one in Release 106.0.1, without having removed the monitor cable, probably because of closing the laptop lid and then reopening it back. It appears to be related to this bug.

Dupe of Bug 1793922.

Status: NEW → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1793922
Priority: -- → P3
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.