Repository navigation
[Flutter GPU] Hot reloading a compute shader dereferences a null render pipeline entry point #193872
Description
Part of #188474.
Hot reloading a shader bundle evicts the pipelines that used each changed shader through PipelineLibrary::RemovePipelinesWithEntryPoint. On Metal, Vulkan and OpenGL ES that function dereferences GetEntrypointForStage(function->GetStage()) for every cached pipeline. Render pipelines have no compute entry point, so reloading a compute shader dereferences a null pointer, and compute pipelines are never evicted at all.
Nothing reaches this today because Flutter GPU cannot create compute pipelines yet. It will crash as soon as #188480 lands.
Changes
- Skip pipelines that have no entry point for the reloaded shader's stage.
- Evict compute pipelines that use the reloaded compute shader.
Testing
A unit test that reloads a compute shader while render and compute pipelines are cached, on Metal and Vulkan.
Dependencies
None.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[Impeller] Evict compute pipelines when their shader is reloaded
[Impeller] Evict compute pipelines when their shader is reloaded
[Impeller] Evict compute pipelines when their shader is reloaded
[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.