https://bugzilla.gnome.org/show_bug.cgi?id=793062
--- Comment #13 from Olivier Fourdan <ofour...@redhat.com> ---
FWIW, I've been running with this patch since yesterday and had no crash in gdk
Wayland code since then.
Not surprising, if the window is withdrawn, the Wayland resources are NULL
(what the see in the GdkWindowImplWayland in comment 8), so by not generating
expose events when the window is withdrawn (attachment 367922), we avoid the
crash.
Yet, I wonder if Firefox is not leaking Wayland resources somehow, I left it
running overnight and today my entire system started to crawl, with ram and
swap up to 90% (the system has 12Gb or RAM) and gnome-shell taking most of
that.
Killing Firefox freed a large part of the memory used by gnome-shell, so I
suspect Firefox might be leaking resources.
However I don't think the leak is caused by the patch (attachment 367922), but
it might be the same root cause.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
