[Bug 401823]
Jeremy Huddleston
jeremyhu at freedesktop.org
Fri Dec 14 08:05:33 UTC 2018
This seems more like a server issue. I think it could easily be possible for
the server to guarantee that XIDs are not reused within a certain time period
since it issued a DestroyNotify. That won't guarantee that clients are happy,
but it can certainly help. We just need to store a timestamp of the time the
XID was destroyed and if the head of the recycle queue is too recent, we
allocate a new XID rather than recycling.
Tracking for 1.12, but I'd consider this for 1.11.x if the change is simple
enough.
--
You received this bug notification because you are a member of Mozilla
Bugs, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/401823
Title:
Gdk-WARNING **: XID collision, trouble ahead
To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/401823/+subscriptions
More information about the Ubuntu-mozillateam-bugs
mailing list