So, reading the spec (specifically, section 3.7), I believe the current mesa behaviour is wrong and you should be perfectly able to eglMakeCurrent(context). Indeed, it looks like you should even be able to call SwapBuffers on thread 2 even without making a context current there.
However, I don't think the proposed solution is correct, either; as I read the spec we actually need the the context (and surface) to have a reference to their own API index, separate to the thread's API index - you can have multiple contexts of different APIs active on a same thread. To the mesa devel lists! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258579 Title: New threads API index different then context after an eglMakeCurrent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1258579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
