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] toImage and toImageSync produce differing pixel contents on Vulkan host tests #193029
On the Vulkan backend (both on Linux and on macOS host tests via MoltenVK), Picture.toImage and Picture.toImageSync produce differing pixel byte outputs for the same recorded canvas operations. This causes the test toImage and toImageSync have identical contents in testing/dart/canvas_test.dart to fail when executed with --impeller-backend=vulkan.
This issue tracks investigating and resolving the rendering or alpha/premultiplication discrepancies between both snapshot paths on Vulkan (replacing legacy closed issue #108835).
Steps to Reproduce
In engine/src/flutter/testing/dart/canvas_test.dart, remove the backend skip condition inside test('toImage and toImageSync have identical contents').
Run the Dart test runner with --impeller-backend=vulkan.
Observed Behavior
The byte data returned by toImage().toByteData() does not match toImageSync().toByteData().
Expected Behavior
Both asynchronous and synchronous snapshot methods should produce identical rasterized pixel buffers across all Impeller backends.
Activity
Fix unawaited async calls in fragment_shader_test and skip Vulkan in …
Allow color delta tolerance in in-memory fuzzy image comparator (flut…
Allow color delta tolerance in in-memory fuzzy image comparator (flut…
Revert: Allow color delta tolerance in in-memory fuzzy image comparat…
[Impeller] Fix SurfaceContextVK submission tracking and double HostBu…