Bug 99263 - XCB spams XCB_GE_GENERIC event after Vulkan window resize
Summary: XCB spams XCB_GE_GENERIC event after Vulkan window resize
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Vulkan/intel (show other bugs)
Version: 13.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
: 99262 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-01-03 20:28 UTC by Rene Lindsay
Modified: 2019-09-18 19:48 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Rene Lindsay 2017-01-03 20:28:56 UTC
I'm using Vulkan to render to a Linux XCB window.
The main message loop uses xcb_poll_for_event(), or xcb_wait_for_event() to receive keyboard, mouse and windowing events.  Everything works as expected, until the user resizes the window, and the app resizes the Vulkan Swapchain accordingly.
Then, I start receiving a non-stop flood of XCB_GE_GENERIC events.

This problem occurs on Ubuntu Unity, Ubuntu Gnome and Fedora Gnome, but only when using Intel Mesa Vulkan drivers.  It does not happen when using proprietary NVidia or AMD graphics drivers.
Comment 1 Rene Lindsay 2017-01-03 20:29:28 UTC
I'm using Vulkan to render to a Linux XCB window.
The main message loop uses xcb_poll_for_event(), or xcb_wait_for_event() to receive keyboard, mouse and windowing events.  Everything works as expected, until the user resizes the window, and the app resizes the Vulkan Swapchain accordingly.
Then, I start receiving a non-stop flood of XCB_GE_GENERIC events.

This problem occurs on Ubuntu Unity, Ubuntu Gnome and Fedora Gnome, but only when using Intel Mesa Vulkan drivers.  It does not happen when using proprietary NVidia or AMD graphics drivers.
Comment 2 Kenneth Graunke 2017-01-03 21:07:25 UTC
*** Bug 99262 has been marked as a duplicate of this bug. ***
Comment 3 GitLab Migration User 2019-09-18 19:48:20 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/827.


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.