Mir

Comment 3 for bug 1362444

Revision history for this message
Kevin DuBois (kdub) wrote :

Okay, so the problem was that the texture cache was using an "invalid ID" to do some of its tracking, and the new IntWrapper-based BufferId doesn't have the concept of an invalid id.

The previous invalid id was "0", so this would only affect the first buffer allocated on the system.

On the android platform, the first buffer allocated is typically the framebuffers (which dont get involved with the texture cache), so thats why I could not reproduce with the demo shells on android. qtmir doesn't use this code, so it wouldn't be affected either.
I could reproduce on mesa, and it would seem to affect only the 1st buffer of the 1st client. Working on fix.