Comment 26 for bug 220628

Revision history for this message
In , Vladimir Vukicevic (vvuk) wrote :

Gonna take this off the blocking list for now; I haven't been able to reproduce it in a VM, and David says he hasn't seen it for a while. From reading the X source and talking to X developers, the two things that could cause it are either a corrupt ID making it over, or running out of XIDs on the X side. The latter would be odd, because we'd probably have run out of memory well before we got to running out of XIDs. The former is possible, but again odd..

Useful information to get if it happens again would be the ID in _XIDHandler, and xrestop information.