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
UberSDF and circle contents heap-allocate std::function captures per draw #192673
UberSDF and circle contents build per-draw callbacks that capture the sampler binding and geometry result by value. Those captures exceed the std::function small-buffer optimization and heap-allocate on every draw.
DrawGeometry invokes the callbacks before returning, so capturing by reference is valid and removes those allocations.
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
mbcorona commentedon Sep 12, 2026
Related to #164607 (the same perf series), not a duplicate.
Routing to the engine team.
[Impeller] Avoid heap-allocating std::function captures per draw (flu…
github-actions commentedon Oct 1, 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.