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
[iOS] App is crashing in production flutter::ImageDecoderImpeller::UploadTextureToStorage #141554
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.16.5, on Microsoft Windows [Version 10.0.19045.3930], locale de-DE)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.7.3)
[√] Android Studio (version 2022.3)
[√] VS Code (version 1.85.1)
[√] Connected device (3 available)
[√] Network resources
Hi @escamoteur
Please provide the stack trace in text format instead of a screenshot for better readability and investigation.
Also, please provide the list of affected device info (OS, model) along with the percentage occurrence of the crash. Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
Thanks for the update. Based on the stack trace, it is somewhat similar to #135524 which is fixed on master channel, but I'm not quite sure. Labeling this for the insights from engine team.
changed the title [-]flutter::ImageDecoderImpeller::UploadTextureToStorage[/-][+][iOS] App is crashing in production `flutter::ImageDecoderImpeller::UploadTextureToStorage`[/+]on Jan 16, 2024
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
huycozy commentedon Jan 15, 2024
Hi @escamoteur
Please provide the stack trace in text format instead of a screenshot for better readability and investigation.
Also, please provide the list of affected device info (OS, model) along with the percentage occurrence of the crash. Thanks!
escamoteur commentedon Jan 15, 2024
huycozy commentedon Jan 16, 2024
Please also share it in text format, it will be easier to copy and search for information.
escamoteur commentedon Jan 16, 2024
escamoteur commentedon Jan 16, 2024
huycozy commentedon Jan 16, 2024
Thanks for the update. Based on the stack trace, it is somewhat similar to #135524 which is fixed on master channel, but I'm not quite sure. Labeling this for the insights from engine team.
1 remaining item
[-]EXC_BAD_ACCESS[/-][+]flutter::ImageDecoderImpeller::UploadTextureToStorage[/+][-]flutter::ImageDecoderImpeller::UploadTextureToStorage[/-][+][iOS] App is crashing in production `flutter::ImageDecoderImpeller::UploadTextureToStorage`[/+]jonahwilliams commentedon Jan 22, 2024
Potentially one of the device buffer or data ptrs is nullptr and we're failing to check this before setting the texture contents.
yoferzhang commentedon Jun 12, 2024
#135524 didn't fix this issue; I can still reproduce it in the Flutter 3.19.5 version.
yoferzhang commentedon Jun 19, 2024
25% of devices have experienced this problem in the past 7 days
escamoteur commentedon Jun 27, 2024
We just got a new one on 3.22
bladeofgod commentedon Jul 12, 2024
Got a same issue on 3.22.1.
device info :
iPhone 15 Pro Max, 17.5.1 (21F90)
some info about it :
jonahwilliams commentedon Aug 31, 2024
As of https://github.com/flutter/engine/pull/54606/files#diff-e549e3a4f8d4dd189a09680c69ca8434bb8ae8031926c47b5e248dd080ae9f9d , we no longer use UploadTextureToStorage. Previously this would run while Flutter had no GPU context which we believed to be crashy.
Since we had no good way to repro, we can't confirm if this is fixed or not.
github-actions commentedon Sep 18, 2024
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.