Re: GLX Pixmap destroy issue
A coworker recently explained this to me. He said that the intent of the GLX spec is that like GLXWindows, only one GLXPixmap should be allowed to be created for a given Pixmap and that subsequent allocations should fail with BadAlloc. However, a bug in the driver allows multiple GLXPixmaps to be created which confuses the dealloc code, which only expects there to be one. The second allocation will fail in future driver releases.