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
[Flutter GPU] ComputePipeline and ComputePass with dispatch #188480
ComputePipeline built from a single compute Shader.
CommandBuffer.createComputePass returning a ComputePass with bindStorageBuffer, bindUniform and bindTexture, plus dispatch(x, y, z) in workgroup counts. The workgroup size comes from the shader.
A zero count is a no-op, matching a draw with zero vertices.
Bindings persist across dispatches within a pass on every backend. Vulkan currently resets them after each dispatch.
A compute pass follows the pass lifecycle in the [Flutter GPU] ☂️ Compute shaders #188474 contract: creating the next pass, recording a copy or readback, or submitting ends it, end() ends it explicitly, and any later use throws a StateError. That lifecycle lands as its own change first.
A kernel writes a buffer that a render pass then draws from, checked through Texture.asImage().toByteData().
A compute pass and a render pass recorded on the same command buffer execute in creation order, and using the compute pass after the render pass was created throws a StateError.
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
[Flutter GPU] Add ComputePipeline and ComputePass
[Flutter GPU] Add ComputePipeline and ComputePass
[Flutter GPU] Add ComputePipeline and ComputePass
[Flutter GPU] Compute shaders on Metal and Vulkan (flutter#193805)
[Flutter GPU] Compute shaders on Metal and Vulkan (flutter#193805)
github-actions commentedon Nov 9, 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.