-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Some animated GIFs don't render frames correctly on Linux #52285
Comments
Tagging subscribers to this area: @safern, @tarekgh Issue DetailsDescriptionWhen using The issues seem to be down in
Configuration
Regression?No. There were worse problems with Other informationI recommend we close this since it's been a longstanding issue, there aren't currently app models that easily surface this scenario, and there haven't been customer reports of it. But I wanted to file it so that we could have the known issue logged.
|
Thank you for the deep investigation, @jeffhandley. As you mentioned in the description, I also think we should close this, but it is a great write up to have here as history so that if a customer ever searches for this, they can find the libgdiplus underlying issues and move to the right place. I will go ahead and close the issue as we have tracking issues on libgdiplus. |
Description
When using
ImageAnimator.Animate
to animate GIFs that use variable frame delays, max loop counts, or partial frame updates, there are issues rendering the frames on Linux.The issues seem to be down in
libgdiplus
and corresponding issues were filed there. This is a tracking issue for the .NET Libraries.Configuration
Regression?
No. There were worse problems with
ImageAnimator
on Linux before #52236. These issues were discovered while adding manual tests for ImageAnimator that capture frame renderings of animations.Other information
I recommend we close this since it's been a longstanding issue, there aren't currently app models that easily surface this scenario, and there haven't been customer reports of it. But I wanted to file it so that we could have the known issue logged.
The text was updated successfully, but these errors were encountered: