[kwin] [Bug 429086] kwin_wayland segmentation faulted in QScopedPointer >::operator->() when usi
https://bugs.kde.org/show_bug.cgi?id=429086 Matt Fagnani changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #4 from Matt Fagnani --- (In reply to Vlad Zahorodnii from comment #3) > We've changed the handling of inert subsurfaces. Is this issue still actual? I haven't seen this type of crash in many months. I think it might've been fixed in Firefox. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429086] kwin_wayland segmentation faulted in QScopedPointer >::operator->() when usi
https://bugs.kde.org/show_bug.cgi?id=429086 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Vlad Zahorodnii --- We've changed the handling of inert subsurfaces. Is this issue still actual? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429086] kwin_wayland segmentation faulted in QScopedPointer >::operator->() when usi
https://bugs.kde.org/show_bug.cgi?id=429086
Matt Fagnani changed:
What|Removed |Added
Version|5.20.3 |5.20.4
--- Comment #2 from Matt Fagnani ---
I've seen kwin_wayland crashes with this trace seven times with Plasma 5.20.3
and six times with 5.20.4. Each crash happened when using Firefox Nightly
84.0a1-86.0a1 on Wayland. All but one crash occurred while moving the cursor
over the bookmark folders. One crash happened on the bugs.kde.org Advanced
search page when I clicked on a popup box in the Custom Search area
https://bugs.kde.org/query.cgi?format=advanced
I've had WebRender compositing enabled in Firefox by going into about:config
and setting gfx.webrender.all=true, gfx.webrender.enabled=true. Having
WebRender enabled might be needed for this crash to happen. Robert Mader
commented "It just occurred to me that with Webrender enabled mesa will commit
our surface in dri2_wl_swap_buffers_with_damage which we call in
GLContextEGL::SwapBuffers(). So even if when using
moz_container_wayland_surface_lock there's still a chance that the surface will
get commited behind our back, potentially freeing it IIUC.
So maybe we have to extent our surface locking to GLContextEGL::SwapBuffers()
as well somehow.
"
https://bugzilla.mozilla.org/show_bug.cgi?id=1655282#c10
Robert wrote a patch to lock the surface in GLContextEGL::SwapBuffers
https://bugzilla.mozilla.org/show_bug.cgi?id=1680961
Checking that the pointer this or d isn't null in
KWaylandServer::SurfaceInterface::subSurface before surface_interface.cpp:792
might avoid the crash at least until the problem is fixed in Firefox.
QPointer< SubSurfaceInterface > SurfaceInterface::subSurface() const
{
return d->subSurface;
}
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 429086] kwin_wayland segmentation faulted in QScopedPointer >::operator->() when usi
https://bugs.kde.org/show_bug.cgi?id=429086 --- Comment #1 from Matt Fagnani --- 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.
[kwin] [Bug 429086] kwin_wayland segmentation faulted in QScopedPointer >::operator->() when usi
https://bugs.kde.org/show_bug.cgi?id=429086 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429086] kwin_wayland segmentation faulted in QScopedPointer >::operator->() when usi
https://bugs.kde.org/show_bug.cgi?id=429086 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
