331–340 of 342 posts
Earlier quoted context omitted.
I'm not suggesting some modest, >1KB spinners should be gated like this. Rather that renderers / apps would put a pause on downloading and processing very large (say 1MB+) or very long animations (100+ frames).
I think you are underestimating gif sizes if you think a 1MB gif is large.
Earlier quoted context omitted.
It is by design, but not that much . That's the point. The machines are designed to use swap and memory compression to greatly enhance responsiveness even with less physical RAM than competitors. And that works well for most users. But there's a bug in the heuristic, and for some users, it starts pathologically swapping. We've seen the numbers go up in the activity monitor. Even while doing ~nothing. Fast. That is ob…
> Terabytes per day of swap activity is not normal, no matter how much these machines are designed to swap on purpose. 1TB is only 62.5 * 16GB. If its paging out 8GB+ apps (quite easy for chrome with a number of tabs) it only takes one memory hog to increase the TBW in a few hours of typical app switching for a mobile app developer. This edge case is pretty extreme, sure, but its still a MINIMUM lifetime of 2 years.…
There is no way this is normal :-)
Earlier quoted context omitted.
It's the only form of video which 1) browsers universally treat as an image file and which automatically, reliably and seamlessly loops and 2) also has wide support outside browsers and user familiarity.
The auto-start and auto-loop might or might not be wanted. The main issue is just how freaking inefficiently huge gifs are for this use case : This whole thread, but also I was seeing an order of magnitude difference in a recent use-case I had, compared to mp4, which would have made sending the document by e-mail otherwise not viable. (And imagine still living somewhere where a Mo of data doesn't have a negligible co…
Earlier quoted context omitted.
> Terabytes per day of swap activity is not normal, no matter how much these machines are designed to swap on purpose. 1TB is only 62.5 * 16GB. If its paging out 8GB+ apps (quite easy for chrome with a number of tabs) it only takes one memory hog to increase the TBW in a few hours of typical app switching for a mobile app developer. This edge case is pretty extreme, sure, but its still a MINIMUM lifetime of 2 years.…
Just FYI, here's an Intel user with the issue. 50% lifetime usage in 7 months. There is no way this is normal :-) https://twitter.com/VE7FIM/status/1396395431941210118?s=19
That user you linked to is using Catalina (as they mention in their twitter thread where they demonstrate a 3% usage increase over 2 weeks), so it will be completely unrelated to the support for silicon, which wasnt added until Big Sur.
My first thought was that each "frame" of the GIF is being expanded/rendered to its own backingstore. GIFs are pretty optimized files — where each "frame" can be a diff from the previous. "De-diffing", converting palette-based pixels to full 24 or 32-bit RGB could really blow up fast.
I'm pretty sure animated gifs only support intra frames.
1. animation isn't technically intended by the gif format [0]:
> Although GIF was not designed as an animation medium, its ability to store multiple images in one file naturally suggested using the format to store the frames of an animation sequence. To facilitate displaying animations, the GIF89a spec added the Graphic Control Extension (GCE), which allows the images (frames) in the file to be painted with time delays, forming a video clip > > To enable an animation to loop, Netscape in the 1990s used the Application Extension block (intended to allow vendors to add application-specific information to the GIF file) to implement the Netscape Application Block (NAB).........Most browsers now recognize and support NAB, though it is not strictly part of the GIF89a specification
2. SMIL[1] is an animation alternative I'd never heard of for the browser.
[0]: https://en.wikipedia.org/wiki/GIF#Animated_GIF [1]: https://en.wikipedia.org/wiki/Synchronized_Multimedia_Integr...
Earlier quoted context omitted.
https://appleinsider.com/articles/21/02/23/questions-raised-... > "While we're looking into the reports, know that the SMART data being reported to the third-party utility is incorrect, as it pertains to wear on our SSDs" said an AppleInsider source within Apple corporate not authorized to speak on behalf of the company. The source refused to elaborate any further on the matter when pressed for specifics. We'll likel…
That Apple comment is bullshit. We've confirmed that the TBW numbers from smartctl match the actual quantity of data written. You can also see the excess I/O in Apple's own Activity Monitor. The lifetime usage numbers smartctl reports are in line with what a high-end SSD would report, and there is no way for smartctl to "make up" the data. It's real data coming from the NVMe controller. There's no possible way to fak…
Earlier quoted context omitted.
And this kids, is why we have key and delta frames. We should drop gif support.
Why not cap animated gifs at a maximum duration or file size? GIFs original use cases are already served by formats better suited to the modern era. Their continued popularity seems due mostly to their historical auto play behavior. One that apps are so reluctant to disrupt we're filling landfills with electronic waste to keep up with ever larger and longer meme animations.
Earlier quoted context omitted.
H.264 level 4.0 seems to have similar behaviors and works on a very wide variety of platforms in my experience. Chrome, Firefox, Edge, Android, and iOS. That covers most of what we want, right? It fails on say... a 2009 era netbook or Android Gingerbread, but we gotta draw the line somewhere. Even if you do care about Android Gingerbread: H264 3.0 Baseline profile IIRC worked on that (though its been a decade, so may…
Can you declare a video as looping, and have that correctly honored everywhere it plays? That has always Just Worked with GIFs, but the last time I checked (a couple of years ago) it basically never worked with any “proper” video format.