linux-traipu team mailing list archive

[Jeremy Huddleston <jeremyhu@xxxxxxxxxxxxxxx>]

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 UBUNTU -
AL - BR, which is subscribed to Chromium Browser.
https://bugs.launchpad.net/bugs/401823

Title:
  Gdk-WARNING **: XID collision, trouble ahead

Status in Chromium Browser:
  Invalid
Status in Mozilla Firefox:
  Invalid
Status in GTK+:
  Expired
Status in xlibs:
  Unknown
Status in firefox package in Ubuntu:
  Fix Released
Status in firefox-3.5 package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in firefox source package in Lucid:
  Invalid
Status in firefox-3.5 source package in Lucid:
  Invalid
Status in gtk+2.0 source package in Lucid:
  Invalid
Status in firefox source package in Karmic:
  Invalid
Status in firefox-3.5 source package in Karmic:
  Won't Fix
Status in gtk+2.0 source package in Karmic:
  Fix Released

Bug description:
  karmic testing

  in .xsession-errors: (firefox:24993): Gdk-WARNING **: XID collision, trouble ahead
  previously, have had this one: (nautilus:3572):
   GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (bug report 401822)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/401823/+subscriptions