-
Notifications
You must be signed in to change notification settings - Fork 677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performance issue on wasm with large (2MB) images #2793
Comments
@oblakr24 Does the issue also occur if you render the image without Coil (i.e. from Compose resources)? |
I see the same lag in the WASM sample, however if I display the same images without Coil I also see the same lag when drawing the image. I think will likely need to be optimized inside CMP/Skiko. |
@colinrtwhite The wasm sample above also stutters heavily on a top-spec M3 Max MBP, so I think this is definitely something to be tracked in the right place. |
I'd report it without Coil on Jetbrains Youtrack for Compose and see what happens. |
@oblakr24 Yep your best bet it to file an issue with Compose Multiplatform or likely the Skiko issue tracker. Skiko is the library that Coil and Compose Multiplatform use to render the images. |
Reported on Skiko issue tracker: |
Describe the bug
Using a standard
AsyncImage
with a string url, when the image itself is larger (i.e. more than 2MB), there is a very significant stutter while the image is rendered.It happens when the image is already loaded or in cache, every time it enters composition.
Does not happen on other platforms (Android, iOS, desktop JVM).
Happens on Chrome, Safari, Firefox.
To Reproduce
Version
3.0.4
The text was updated successfully, but these errors were encountered: