mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-16 01:08:05 +02:00
7b0e8264dd
We were using a sequence counter value to wait for a specific NotifyMSC event. However, we can receive events from other clients as well, which may already be using higher sequence numbers than us. In that case, we could stop processing after an event from another client, which could have been received significantly earlier. This would have multiple undesirable effects: * The computed MSC and UST values would be lower than they should be * We could leave a growing number of NotifyMSC events from ourselves and other clients in XCB's special event queue I ran into this with Firefox and Thunderbird, whose VSync threads both seem to use the same window. The result was sluggish screen updates and growing memory consumption in one of them. Fix this by checking the XCB sequence number and MSC value of NotifyMSC events, instead of using our own sequence number. v2: * Use the Present event ID for the sequence parameter of the PresentNotifyMSC request, as another safeguard against processing events from other clients * Rebase on drawable mutex changes Reviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com> # v1 |
||
|---|---|---|
| .. | ||
| Android.mk | ||
| loader.c | ||
| loader.h | ||
| loader_dri3_helper.c | ||
| loader_dri3_helper.h | ||
| Makefile.am | ||
| Makefile.sources | ||
| meson.build | ||
| pci_id_driver_map.c | ||
| pci_id_driver_map.h | ||
| SConscript | ||