Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

An Animated GIF displays, i.e. moves, for about 5 minutes, then freezes. Other GIFs from the site work indefinitely, and this GIF works indefinitely on IE. Why does it freeze in Firefox?

  • 2 biyano
  • 5 eza na bankokoso oyo
  • 5 views
  • Eyano yasuka ya CouldBeWorse

more options

An Animated Avatar GIF file moves as expected for about 5 minutes, and then freezes. Other animated avatars from the same site work fine, and move indefinitely. To confirm that the site had not exchanged the file for a non-animated version, I right-clicked and selected 'View Image Info' and when I did so, it moved for about half a second. (The image file was the one uploaded.) Loaded the page in IE, this avatar moves indefinitely. Any ideas why an animated GIF stops in Firefox?

An Animated Avatar GIF file moves as expected for about 5 minutes, and then freezes. Other animated avatars from the same site work fine, and move indefinitely. To confirm that the site had not exchanged the file for a non-animated version, I right-clicked and selected 'View Image Info' and when I did so, it moved for about half a second. (The image file was the one uploaded.) Loaded the page in IE, this avatar moves indefinitely. Any ideas why an animated GIF stops in Firefox?

All Replies (2)

more options

Hello? ...anybody there? ...or is the statement "The Firefox community is here to help!" on the Questions page like: "Your check's in the mail".

more options

The answer is that Animated GIF files include a Loop Enable Flag as well as a Loop Limit Count. This GIF had a count which should have allowed it to loop for almost 2 hours. But in Firefox it only loops for about 5 minutes.

It appears Firefox is misinterpreting this value to be a Frame Count rather than a Cycle Count.

Is there any Firefox Employees reading this, and can acknowledge this has been added to their Opportunity (a.k.a. Bug) List?