Bug 1676890 - firefox-wayland crashes gnome-shell when ff tab is dragged out and moved between monitors in multi monitor setup
Summary: firefox-wayland crashes gnome-shell when ff tab is dragged out and moved be...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 29
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
 
Reported: 2019-02-13 14:13 UTC by Mateusz Mojsiejuk
Modified: 2019-07-11 10:54 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-11 10:54:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
gnome-shell backtrace (13.79 KB, text/plain)
2019-02-20 21:15 UTC, Mateusz Mojsiejuk
no flags Details
tailf of journalctl (4.32 KB, text/plain)
2019-02-20 21:18 UTC, Mateusz Mojsiejuk
no flags Details

Description Mateusz Mojsiejuk 2019-02-13 14:13:35 UTC
Description of problem:


Version-Release number of selected component (if applicable):

Fedora 29 ,  

firefox-wayland-65.0-4.fc29.x86_64


How reproducible:
100% 

Steps to Reproduce:
1. Start firefox-wayland, have multiple tabs open in ff.
2. Pull one tab out and move it to secondary monitor and back a couple of times
3. Behold results

Actual results:
Gnome-shell hangs completely and stops updating screen (sound is still coming through so believe all processes keep running)


Expected results:
Window should move between the two monitors in a multi-monitor setup


Additional info:
hard - resetting and booting again and the computer works
but if you start firefox-wayland again and it has restore previous sessions
enabled you will trigger the same bug causing an instant crash of gnome-shell again.

One has to start ff with another profile , or start the non wayland version of firefox to undo the tab on the secondary screen.

Comment 1 Jonas Ådahl 2019-02-19 10:23:44 UTC
After having installed the debug symbols of the mutter and gnome-shell packages, can you run the following:

sleep 10 && pstack $(pgrep -u $USER -x gnome-shell) >& gnome-shell-backtrace.txt

then within 10 seconds, reproduce the freeze you are experiencing? It should hopefully log where gnome-shell got stuck. Attach the resulting file here. A piece of the journal from when gnome-shell got stuck would help as well.

Comment 2 Mateusz Mojsiejuk 2019-02-20 21:15:21 UTC
Created attachment 1536860 [details]
gnome-shell backtrace

Comment 3 Mateusz Mojsiejuk 2019-02-20 21:18:42 UTC
Created attachment 1536861 [details]
tailf of journalctl

Comment 4 Mateusz Mojsiejuk 2019-02-20 21:20:16 UTC
The attached files above were generated on firefox-wayland-65.0.1-1.fc29.x86_64

Comment 5 Jonas Ådahl 2019-02-28 13:25:55 UTC
Any chance to get get a backtrace with debug symbols (for mutter, gnome-shell and glib)?

Comment 6 Mateusz Mojsiejuk 2019-03-22 10:55:26 UTC
I can no longer reproduce the issue, So I think it can be set to solved.

possibly in the firefox release yesterday as I noticed I'm on:
firefox-wayland-66.0-6.fc29.x86_64 now

Comment 7 Martin Stransky 2019-07-11 10:54:24 UTC
Thanks!


Note You need to log in before you can comment on or make changes to this bug.