Bug 415256 - Random Segmentation fault while Firefox open
Summary: Random Segmentation fault while Firefox open
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: platform-wayland-nested (show other bugs)
Version: 5.17.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-16 18:29 UTC by pyro4hell
Modified: 2020-03-19 15:14 UTC (History)
0 users

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


Attachments
dmesg output of the latest two segfaults (12.51 KB, text/plain)
2019-12-16 18:29 UTC, pyro4hell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pyro4hell 2019-12-16 18:29:05 UTC
Created attachment 124532 [details]
dmesg output of the latest two segfaults

SUMMARY

Sometimes while browsing with firefox kwin on wayland has a segmentation fault. The mouse and screen freezes and the session is destroyed putting me at the sddm login screen

STEPS TO REPRODUCE
1. log in with kwin-wayland
2. start firefox
3. have some bad luck

OBSERVED RESULT
session freeze, segmentation fault in kwin, Qt5Core, libKF5WaylandServer

EXPECTED RESULT
smooth wayland session

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION
firefox is run in xwayland mode, as the `MOZ_ENABLE_WAYLAND=1 firefox` produces a firefox which canvas does not update

attached two dmesg outputs taken directly after the session segfaultet.
Below the first line of each dmesg output


    [ 6330.869592] kwin_wayland[1299]: segfault at 1961 ip 00007f76d82b1ae3 sp 00007ffddc991550 error 6 in libQt5Core.so.5.13.2[7f76d81fb000+2ea000]

    [ 4755.205082] traps: kwin_wayland[714] general protection ip:7f02b5ba16ea sp:7ffd34aff120 error:0 in libKF5WaylandServer.so.5.64.0[7f02b5b56000+62000]
Comment 1 pyro4hell 2020-01-15 21:06:52 UTC
another one just now, and one during writing this message

[10489.483756] kwin_wayland[741]: segfault at 29e62db1006a ip 00007f60cf68c9ee sp 00007ffcdc599630 error 4 in libKF5WaylandServer.so.5.66.0[7f60cf641000+63000]
[10489.483763] Code: 08 48 85 d2 74 04 f0 83 02 01 4c 89 e0 41 5c c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 41 54 49 89 fc 48 89 f7 ff 15 ca c5 05 00 <48> 8b 90 38 02 00 00 48 8b 80 40 02 00 00 49 89 14 24 49 89 44 24
[10489.483836] audit: type=1701 audit(1579122098.257:105): auid=1000 uid=1000 gid=100 ses=2 pid=741 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1


[10648.776086] kwin_wayland[4507]: segfault at 40 ip 00007fe7ee7fc8c0 sp 00007ffe843e8578 error 4 in libKF5WaylandServer.so.5.66.0[7fe7ee7e6000+63000]
[10648.776094] Code: 00 75 21 48 83 c4 10 5d 41 5c 41 5d c3 0f 1f 44 00 00 ba 08 00 00 00 be 02 00 00 00 ff 15 80 f7 08 00 eb cf ff 15 e0 f0 08 00 <48> 8b 06 48 89 07 8b 10 85 d2 74 14 83 fa ff 75 07 c3 66 0f 1f 44
[10648.776174] audit: type=1701 audit(1579122257.548:151): auid=1000 uid=1000 gid=100 ses=4 pid=4507 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1
Comment 2 pyro4hell 2020-01-16 21:29:07 UTC
another one, different error message

[ 7373.624905] traps: kwin_wayland[739] general protection ip:7fd4db3c2183 sp:7ffd65b82c80 error:0 in libQt5Core.so.5.14.0[7fd4db343000+2f8000]
Comment 3 pyro4hell 2020-01-30 22:15:07 UTC
another one

[15546.198956] kwin_wayland[726]: segfault at 297f5dfd31ec ip 00007f8d2093d9ee sp 00007ffd08ac5410 error 4 in libKF5WaylandServer.so.5.66.0[7f8d208f2000+63000]
[15546.198965] Code: 08 48 85 d2 74 04 f0 83 02 01 4c 89 e0 41 5c c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 41 54 49 89 fc 48 89 f7 ff 15 ca c5 05 00 <48> 8b 90 38 02 00 00 48 8b 80 40 02 00 00 49 89 14 24 49 89 44 24
Comment 4 Vlad Zahorodnii 2020-03-19 09:55:43 UTC
Could you please attach a backtrace to this bug report? You would need to ssh from another computer. https://community.kde.org/KWin/Debugging
Comment 5 pyro4hell 2020-03-19 15:14:43 UTC
Thank you for your reply. I haven't had this Segfault since my last comment on 2020-01-30. So one and a half month. I suspect it got fixed (or I now have more good luck)

Closing