Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak

twitter.com

Post reply on HN
Print view View original

271–280 of 342 posts

Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak

#271

Post by sgerenser »

asddubs wrote: post #232
unfunco wrote: post #224

Earlier quoted context omitted.

I bought the 2011 MacBook Air 11" and it still performs really well for everyday tasks, probably the best computer I've ever owned.

Interesting, I wonder why mine slowed down so much then. From what I remember it was after an OS upgrade, it was my first time trying a mac, and I ended up being disappointed and going back to linux, but I also didn't do a deep dive into figuring out the reasons for it.

I believe the 2011 era MacBook Air (EveryMac.com confirms only the 11”) had an entry level 2GB RAM variant. That one probably got pretty painful after just a couple OS updates.

Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak

#272

Post by Angostura »

colejohnson66 wrote: post #266
colanderman wrote: post #220

Earlier quoted context omitted.

6502 is arguably a "proto-ARM", so one could say Apple has come full circle.

What do you mean “proto ARM”? I thought the 6502 was based on the MC6800 (the predecessor to the 68k)?

No the 6502 was Chuck Peddle's baby - not related.

It had a quite a nice simple instructions set.

Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak

#273

Post by iainmerrick »

dragontamer wrote: post #265
FalconSensei wrote: post #262

Earlier quoted context omitted.

> We should drop gif support. We just need an actual replacement that has the same behaviours and actually works everywhere, as gif does. Videos are not a replacement, and other image formats don't work everywhere

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.

Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak

#274

Post by sgerenser »

smoldesu wrote: post #246
can16358p wrote: post #39

Earlier quoted context omitted.

MacBooks can easily exceed 10+ years rock solid. (Only battery may need a replacement)

Not anymore? It's not like battery replacement is very viable on modern Macs, and the SSD wear issue means that most of these "daily driver" machines will end up dead in more like 3 or 4 years. But yes, older Macs were notorious for being great machines.

While I’d much prefer if the SSDs were replaceable, I don’t think there’s any evidence that Apple SSDs were failing or will fail in only 3-4 years.

Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak

#275

Post by jiofih »

BoorishBears wrote: post #142
jiofih wrote: post #97

Earlier quoted context omitted.

Where do you see anything about individually opening 730 frames, and why would it be unsurprising for that tiny load to cause a bug? Have you heard of video editors? The same machine can edit four 4K@60fps streams.

Thanks for making my point, the program is indeed opening individual frames. And what are you on about after that? No one said it's unsurprising for that to cause a bug. It's saying that the gif is not cause here, an editor is coming across a framework call that's blowing up Call it an editor bug, or a framework bug, it's not an image using the memory, it's the editor

Oh my god. I get it. You’re reading the headline as “this GIF uses xx memory”. That’s not what is says. It’s “GIF uses X memory on x86, X*10 memory on M1”. You’re picking a fight based on your own misreading.

Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak

#277

Post by Andrex »

FalconSensei wrote: post #262
slver wrote: post #149

Earlier quoted context omitted.

And this kids, is why we have key and delta frames. We should drop gif support.

> We should drop gif support. We just need an actual replacement that has the same behaviours and actually works everywhere, as gif does. Videos are not a replacement, and other image formats don't work everywhere

Animated PNG is supported in every single modern browser, and degrades gracefully (the first frame is at least rendered.)

https://www.caniuse.com/apng

WebP support (including animation) was added to the most recent major version of Safari, meaning WebP has similarly widespread support.

https://www.caniuse.com/webp

Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak

#278

Post by dragontamer »

iainmerrick wrote: post #273
dragontamer wrote: post #265

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.

Most of gfycat's traffic these days is .mp4 files that pretend to be gifs. Even if you upload a gif, its converted into .mp4 because its a far more efficient transmission codec.

I'm sure there's some javascript / backend logic that handles some corner cases. But... yeah. A lot of self-looping .mp4 stuff seems to be solved. The tag has been getting more and more consistent these days.

I just do some hobby stuff though. I only test on the stuff close to me (chrome, edge, firefox, my phone). So I can't say too much about reliability on older / more obscure platforms.

Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak

#279

Post by dragontamer »

FalconSensei wrote: post #269
dragontamer wrote: post #265

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 I just upload a H.264 level 4.0 video anywhere where an image is allowed and it will be displayed as an image? Will it be displayed as an image in any forum, chat/messenger platform? Can I use it as my avatar in places that allows for gif avatars, like Mastodon? edit: grammar

Hmm, I'm thinking about the Web-browser level (Chrome / Edge / Firefox) instead of say, web-application layer (ie: PHPbb vs XenForo).

The web browsers seems to have significantly improved compatibility of in recent years, and even had decent compatibility 10 years ago (if you use Baseline profile H.264 3.0 videos and Javascript to smooth over some edges).

Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak

#280

Post by Toutouxc »

smoldesu wrote: post #246
can16358p wrote: post #39

Earlier quoted context omitted.

MacBooks can easily exceed 10+ years rock solid. (Only battery may need a replacement)

Not anymore? It's not like battery replacement is very viable on modern Macs, and the SSD wear issue means that most of these "daily driver" machines will end up dead in more like 3 or 4 years. But yes, older Macs were notorious for being great machines.

> It's not like battery replacement is very viable on modern Macs

Why? Apple still offers battery replacements for modern Macs, and some more adventurous types of people still do it themselves. They're glued to the chassis, not spot welded.

Post reply on HN