Bug 106620 - Xwayland crashed when I try return to desktop while playing game MAD MAX
Summary: Xwayland crashed when I try return to desktop while playing game MAD MAX
Status: RESOLVED FIXED
Alias: None
Product: Wayland
Classification: Unclassified
Component: XWayland (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Wayland bug list
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-22 19:31 UTC by mikhail.v.gavrilov
Modified: 2018-09-27 10:39 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xwayland backtrace (17.43 KB, text/plain)
2018-05-22 19:31 UTC, mikhail.v.gavrilov
Details
Xwayland backtrace (3.00 KB, text/plain)
2018-06-12 19:44 UTC, Roman Gilg
Details

Description mikhail.v.gavrilov 2018-05-22 19:31:21 UTC
Created attachment 139684 [details]
Xwayland backtrace

Xwayland crashed when I tried return to desktop while playing game MAD MAX (pressed Alt + Tab)
This happens one times, and I unable it reproduce again.
Comment 1 Olivier Fourdan 2018-05-22 19:54:03 UTC
Crash is in Xwayland present code.
Comment 2 Roman Gilg 2018-05-23 09:15:20 UTC
It maybe only happened once because it seems to happen when a sync-event is still pending from the Wayland server, what is a very small part of a full refresh cycle.

It's weird that the crash happened after the sync event triggered present_wnmd_event_notify very late in present_send_complete_notify's call to present_window_priv. I would have assumed such a crash could only happen earlier. Does this mean the private window struct is suddenly gone?
Comment 3 Roman Gilg 2018-06-12 19:44:21 UTC
Created attachment 140141 [details]
Xwayland backtrace

It seems exactly this crash just happened to me as well when trying to launch Steam.

The "Updating Steam Information.." dialog appeared and afterwards my session froze.
Comment 4 Roman Gilg 2018-09-27 10:39:21 UTC
Should be fixed with ce271535adb697.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.