Repository navigation
Closed
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work lista: desktopRunning on desktopRunning on desktopa: imagesLoading, displaying, rendering imagesLoading, displaying, rendering imagesc: renderingUI glitches reported at the engine/skia or impeller rendering levelUI glitches reported at the engine/skia or impeller rendering levelengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.found in release: 3.13Found to occur in 3.13Found to occur in 3.13found in release: 3.14Found to occur in 3.14Found to occur in 3.14frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onteam-engineOwned by Engine teamOwned by Engine teamtriaged-engineTriaged by Engine teamTriaged by Engine team
Description
this webp image is ok preview on chrome
[ +320 ms] E/flutter (31817): [ERROR:flutter/lib/ui/painting/multi_frame_codec.cc(112)] Could not getPixels for frame 2
[ +113 ms]
══╡ EXCEPTION CAUGHT BY IMAGE RESOURCE SERVICE ╞════════════════════════════════════════════════════
The following _Exception was thrown resolving an image frame:
Exception: Codec failed to produce an image, possibly due to invalid image data.
When the exception was thrown, this was the stack:
...
Image provider: AssetImage(bundle: null, name: "assets/test.webp")
Image key: AssetBundleImageKey(bundle: PlatformAssetBundle#8e3b4(), name: "assets/test.webp", scale:
1.0)
════════════════════════════════════════════════════════════════════════════════════════════════════
Reacted by Pedro Neto, NPL and Bart Selwesiuk
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work lista: desktopRunning on desktopRunning on desktopa: imagesLoading, displaying, rendering imagesLoading, displaying, rendering imagesc: renderingUI glitches reported at the engine/skia or impeller rendering levelUI glitches reported at the engine/skia or impeller rendering levelengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.found in release: 3.13Found to occur in 3.13Found to occur in 3.13found in release: 3.14Found to occur in 3.14Found to occur in 3.14frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onteam-engineOwned by Engine teamOwned by Engine teamtriaged-engineTriaged by Engine teamTriaged by Engine team
Activity
asashour commentedon Jul 5, 2021
I am able to reproduce on
desktop. It works fine withweb, usingmaster.flutter doctor -v
[-]can not decode some webp image[/-][+][desktop] Some webp fails to laod, throws `multi_frame_codec.cc(112)] Could not getPixels for frame 2`[/+]TahaTesser commentedon Jul 5, 2021
Hi @wasabia
Thanks for filing the issue, I can reproduce the issue only on the desktop on Windows, Linux, and macOS. While it loads on the web.
Used the following minimal code sample
minimal code sample
logs
stablemasterCheck
flutter doctor -voutputs for each channel belowflutter doctor -v
✅ : No Issue ❌: Issue reproduced
Investigation
When running the app, first frame is laoded and then the error is shown. Which fits the error message as it says
Could not getPixels for frame 2Source of the error message
[-][desktop] Some webp fails to laod, throws `multi_frame_codec.cc(112)] Could not getPixels for frame 2`[/-][+][desktop] Some webp fails to load, throws `multi_frame_codec.cc(112)] Could not getPixels for frame 2`[/+]13 remaining items
flutter-triage-bot commentedon Aug 18, 2023
The
triaged-desktoplabel is irrelevant if there is noteam-desktoplabel orfyi-desktoplabel.Gi-lo commentedon Aug 21, 2023
Hey, adding some findings from our team:
This might be related to either the used color model (YUV vs RGB) or the used compression (VP8 vs WebP Intern) which differ on lossy vs lossless webps.
We fixed the issue in our scenario by pre-processing the webps on our server before sending them out to our application.
pavanpodila commentedon Sep 24, 2024
This is still a problem in Flutter 3.24.3 with WebP in iOS Simulator
bselwe commentedon Jan 26, 2026
This still happens for animated WebPs on Flutter 3.38.5, reproduced on iOS 16 Pro (iOS 26.2), with the following network image:
[engine] Decode animation frames with alpha after an opaque first fra…
github-actions commentedon Oct 13, 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.