You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a bunch of threads, a bunch of EGL contexts, and a bunch of methods which either assume a current GL context or setup a context on entry and tear it down on exit.
This is both doing unnecessary work (unbinding an EGL context implies a GL flush) and is a source of potential pitfalls - an EGL context can only be current on a single thread (so if we happen to need to access a context from multiple threads, it will fail), and there can only be one context current on a thread (so when we do the make_current on entry and release_current on exit dance we may have broken the caller).
This discussion was converted from issue #1124 on May 03, 2023 09:51.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have a bunch of threads, a bunch of EGL contexts, and a bunch of methods which either assume a current GL context or setup a context on entry and tear it down on exit.
This is both doing unnecessary work (unbinding an EGL context implies a GL flush) and is a source of potential pitfalls - an EGL context can only be current on a single thread (so if we happen to need to access a context from multiple threads, it will fail), and there can only be one context current on a thread (so when we do the
make_current
on entry andrelease_current
on exit dance we may have broken the caller).Beta Was this translation helpful? Give feedback.
All reactions