On Fri, 7 May 2010, Mattias Brink wrote:
> X Error of failed request: BadIDChoice (invalid resource ID chosen for this
> connection)
> Major opcode of failed request: 148 (RENDER)
> Minor opcode of failed request: 4 (RenderCreatePicture)
> Resource id in failed request: 0x70d095
> Serial number of failed request: 39781714
> Current serial number in output stream: 39782022
Sadly I have to report that we've been seeing a higher occurrence of these
type of X or GLX errors too, recently. As you'll see from previous threads
on the problem is probably a timing one, but is intermittent and therefore
very difficult to diagnose. It seems to be affected by OS kernel/OpenGL
driver/graphics hardware combinations too, which makes it even harder to
diagnose. However, in my experience, one way to virtually guarantee a
failure like this is to try running analysis over ssh with X forwarding -
perhaps this might allow the (or one of the..) offending timing issue to
be tracked down?
--
Dr. Brian O. Smith ---------------------- B Smith at bio gla ac uk
Division of Molecular & Cellular Biology,
Faculty of Biomedical & Life Sciences,
Joseph Black Building, University of Glasgow, Glasgow G12 8QQ, UK.
Tel: 0141 330 5167/6459/3089 Fax: 0141 330 4600
-------------------------------------------------------------------
The University of Glasgow, charity number SC004401
|