https://bugs.kde.org/show_bug.cgi?id=429086
--- Comment #1 from Matt Fagnani <matthew.fagn...@utoronto.ca> --- I've seen kwin_wayland crashes with this trace four times now. Each crash happened when using Firefox 84.0a1-85.0a1 on Wayland and moving the cursor over the bookmark folders. The folder shown at the time of the crash didn't contain another folder during two of the crashes, so the bookmark folder having another folder in it isn't a requirement for reproducing the crash. Another of the crashes had the contents of a bookmark folder within a folder frozen in a state of disappearing when Plasma crashed. Firefox on Wayland crashed many times when using the bookmarks folders during the last four months or so in Plasma 5.19.5 and earlier. Segmentation faults happened involving a null pointer dereference in wl_proxy_marshal_constructor at wayland-client.c:830 in libwayland-client-1.18.0-2.fc33.x86_64. The Wayland proxies of the surfaces of the bookmark folders might've been occasionally freed before being used. I reported the Firefox crashes at https://bugzilla.mozilla.org/show_bug.cgi?id=1655282 If the Wayland subsurface of the bookmark folders were sometimes freed before being used, this=0x0 in KWaylandServer::SurfaceInterface::subSurface in frame 1 might be how that would show up. I reported these crashes for Fedora at https://bugzilla.redhat.com/show_bug.cgi?id=1897969 kwin_wayland core dump files were truncated for other crashes because their uncompressed sizes were above the 2 GB default limit of systemd-coredump https://bugs.kde.org/show_bug.cgi?id=416974 I changed /etc/systemd/coredump.conf many months ago to have the following values so the kwin_wayland core dumps wouldn't be truncated: ProcessSizeMax=3G ExternalSizeMax=3G -- You are receiving this mail because: You are watching all bug changes.
