Bug 404912 - KWin crashes on KWayland::Server::SurfaceInterface::lockedPointer()
Summary: KWin crashes on KWayland::Server::SurfaceInterface::lockedPointer()
Status: RESOLVED DUPLICATE of bug 393627
Alias: None
Product: kwin
Classification: Plasma
Component: platform-wayland-nested (show other bugs)
Version: 5.15.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-28 16:09 UTC by Erin Yuki Schlarb
Modified: 2019-03-11 08:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Backtrace of main thread (can supply backtraces for other threads if useful) (20.60 KB, text/plain)
2019-02-28 16:09 UTC, Erin Yuki Schlarb 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Erin Yuki Schlarb 2019-02-28 16:09:07 UTC 
Created attachment 118438 [details]
Backtrace of main thread (can supply backtraces for other threads if useful)

SUMMARY
KWin crashes regularily for me and I could reproduce the attached backtrace from several of its core dumps. The line about lockedPointer looks like it may be hint about what is happening, although I do not have a test case for this right now.

STEPS TO REPRODUCE
Don't know yet, but I have several collected several KWin coredumps/crashes already (so it is reproducible)
Looking at the backtrace leads me to believe that devs may be able to infer from it what is happening.

OBSERVED RESULT
KWin dumps core and disappears.

EXPECTED RESULT
KWin doesn't do that.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 10 with KDE Neon User packages running Linux 4.19.20-1
KDE Plasma Version: 4:5.15.2-0xneon+18.04+bionic+build28
KDE Frameworks Version: 4:5.55.0-0xneon+18.04+bionic+build20
Qt Version: 5.12.0+dfsg-0+xneon+18.04+bionic+build54

ADDITIONAL INFORMATION
GPU Driver: amdgpu on Radeon R9 M280X
Comment 1 Vlad Zahorodnii 2019-03-11 08:53:29 UTC 
*** This bug has been marked as a duplicate of bug 393627 ***