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
{{ message }}
Repository navigation
[Impeller] [OpenGL] Use the IO context for OpenGL program setup. #176657
The IO context when using OpenGL is in the same sharegroup as the render context. Since the handle tables are shared, is should be possible to construct OpenGL programs on the IO thread in addition to the render thread.
Setup and verify that the OpenGL backend uses at least two threads to setup PSOs.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
Re-prioritize pipeline compile jobs and perform them eagerly instead …
Re-prioritize pipeline compile jobs and perform them eagerly instead …
Re-prioritize pipeline compile jobs and perform them eagerly instead …
Re-prioritize pipeline compile jobs and perform them eagerly instead …
Re-prioritize pipeline compile jobs and perform them eagerly instead …
Re-prioritize pipeline compile jobs and perform them eagerly instead …
Re-prioritize pipeline compile jobs and perform them eagerly instead …
Re-prioritize pipeline compile jobs and perform them eagerly instead …
Re-prioritize pipeline compile jobs and perform them eagerly instead …
[Impeller] Use the IO context for OpenGL program setup (#37)
[Impeller] Use the IO context for OpenGL program setup (flutter#37)
[Impeller] Use the IO context for OpenGL program setup (#37)
[Impeller]Use the IO context for OpenGL program setup (flutter#185723)
[Impeller] Use the IO context for OpenGL program setup (#37)
github-actions commentedon Aug 6, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.