Description of problem:
This seems to happen *sometimes* when you press Shift+F10 in Nautilus to display a context menu for the selected file (not sure if right mouse click can trigger the same crash). This exact crash happened to me twice already just today. The whole session dies just because of that, and all my unsaved work in all apps is lost.
Version-Release number of selected component:
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor: Fedora Project
runlevel: N 5
Thread no. 1 (10 frames)
#0 meta_wayland_surface_get_toplevel at wayland/meta-wayland-surface.c:1750
#1 meta_wayland_surface_get_toplevel_window at wayland/meta-wayland-surface.c:1761
#2 meta_surface_actor_wayland_get_scale at compositor/meta-surface-actor-wayland.c:104
#3 meta_surface_actor_wayland_sync_state at compositor/meta-surface-actor-wayland.c:196
#4 actor_surface_commit at wayland/meta-wayland-surface.c:2010
#5 xdg_popup_role_commit at wayland/meta-wayland-xdg-shell.c:603
#6 meta_wayland_surface_role_commit at wayland/meta-wayland-surface.c:1891
#7 apply_pending_state at wayland/meta-wayland-surface.c:700
#8 ffi_call_unix64 at ../src/x86/unix64.S:76
#9 ffi_call at ../src/x86/ffi64.c:525
Created attachment 1197943 [details]
Created attachment 1197944 [details]
Created attachment 1197945 [details]
Created attachment 1197946 [details]
Created attachment 1197947 [details]
Created attachment 1197948 [details]
Created attachment 1197949 [details]
Created attachment 1197950 [details]
Created attachment 1197951 [details]
Created attachment 1197952 [details]
Created attachment 1197953 [details]
Created attachment 1197954 [details]
Created attachment 1197955 [details]
Does this still happen with 3.21.91? The changes between 3.21.90 and 3.21.91 changes a lot of things where the backtrace shows it crashed.
Interesting, I do this often, but on Fedora 24/gnome-shell 3.20.4 (on Wayland). Could be a regression?
Could have, at some point during 3.21.x, but I believe its likely that its fixed by 3.21.91.
(In reply to Jonas Ådahl from comment #14)
> Does this still happen with 3.21.91?
Unfortunately bug 1373372 prevents from from updating gtk3, which prevents me from updating mutter (causes other issues), which prevents me from updating gnome-shell. Will test once I'm able to update gnome-shell.
Seems to be working now with:
Will reopen if it happens again.
I'm seeing a similar crash, and I can reproduce it almost 100% of the time in 3.21.91 as well as mutter and gnome-shell that I built from the latest git:
- Open gnome-terminal
- Press left and right mouse buttons simultaneously (they need to be handled as separate buttons - i.e., middle button emulation needs to be OFF)
This crashes gnome-shell immediately.
The backtrace in gdb looks bizarre:
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
meta_wayland_surface_get_toplevel (surface=0x0, surface@entry=0xb5a790) at wayland/meta-wayland-surface.c:1689
1689 if (surface->role)
See the "surface" and "surface@entry": the correct value was passed into the function, but it somehow became NULL, even before the first line of the function got executed.
I set a breakpoint in "meta_wayland_surface_get_toplevel" to see what happens before the crash. It gets called lots of times; usually, surface and surface@entry are equal - but not always, e.g.:
Thread 1 "gnome-shell" hit Breakpoint 1, meta_wayland_surface_get_toplevel (surface=0xb5ace0, surface@entry=0xfe6370)
1689 if (surface->role)
I have no explanation for what's happening. Memory corruption? Concurrency issue? I'm guessing it's some kind of race condition given that it happens only when two events happen at almost the same time, but they're all processed by the main thread, right?
(In reply to Dima Ryazanov from comment #19)
> I'm seeing a similar crash, and I can reproduce it almost 100% of the time
> in 3.21.91 as well as mutter and gnome-shell that I built from the latest
> - Open gnome-terminal
> - Press left and right mouse buttons simultaneously (they need to be handled
> as separate buttons - i.e., middle button emulation needs to be OFF)
I can reproduce that 100%, I filed a new bug 1376447. Please continue the discussion in that bug, thanks.