Comment # 37 on bug 75279 from Ilia Mirkin

(In reply to comment #36)
> Can you reproduce yourself by running the attached glxtest program in
> valgrind?

Oh, I'm sure (can't right now, will try tonight). But I doubt it's the source
of the bug. The glxtest program doesn't appear to hang. Memory is unlikely to
be reallocated _so_ quickly, that ->state would change. (Although more likely
in a multithreaded program... hm.)