Earlier quoted context omitted.
It sometimes feel like it is a bonus today, if apps bother to clean up their memory at runtime, so maybe that's why parent poster thought it is a good and special thing, that the OS free's the memory of an ended processes. Btw. many people don't seem to know, that also in languages with a garbage collector like Javascript, you can create awesome memory leaks. And I would bet, most websites actually do: it only works,…
I have 32GB of RAM and it sits unused most of the time. Right now I am at 4GB/32GB. It simply isn't a significant source of memory consumption. Open Atom and you can easily get to 500MB for a single application, which is completely wasteful. That browser can run dozens of apps in 4GB.
Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak
171–180 of 342 posts
Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak
#172Who else is excited that we are might revive the 80s Cambrian explosion of different system system and architectures? Back then there were so many options.
Hmmm... the chances for that are pretty slim I'm afraid. "Apple Silicon" is not a new system, it's just one of the large incumbents switching to another architecture (which is also not a first, this now being their fourth architecture, after 680x0, PowerPC and x86). In the desktop/notebook market, Wintel and Apple are firmly entrenched, with only ChromeOS and Linux challenging them - plus a few less significant OSes…
Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak
#173Earlier quoted context omitted.
Wow. This can explain some of excesive swap usage on M1.
Seems like a poor conclusion to draw with this little information.
Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak
#174Who else is excited that we are might revive the 80s Cambrian explosion of different system system and architectures? Back then there were so many options.
Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak
#175Earlier quoted context omitted.
Wouldn't 4 to 5 years of full-day usage be just fine for worst case life expectancy for a laptop? I've had one that gave up on 3 years, a couple months after warranty ended (that seemed to be quite common for that brand at the time).
Enterprise Thinkpads easily last 10+ years. Although you will need to change the battery at some point. I think my current work laptop is 6-7 years old. My backup laptop is 11 years old.
That said, my 2015 HP Zbook (previously in contracting work, now personal use) still works perfectly, only now with third keyboard, third battery, and a bit of superglue.
Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak
#176Earlier quoted context omitted.
Browsers and other players will generally be fine, as they render the image progressively. However, editors /processing tools which attempt to load it as a series of frames or a video will usually break, as memory consumption explodes, unless they have a smart disk buffer system to handle it. I wouldn't be surprised if some poorly implemented players were built on top of abstraction layers that end up flattening the…
And this kids, is why we have key and delta frames. We should drop gif support.
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.
Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak
#177Even 360MB seemed a bit high to me so I had to open it up in a few apps to get some perspective. Ristretto: 48.8MB. EOG: 51.3MB. ImageMagick: 169MB. Firefox: 305.1MB. Vivaldi: 185.2MB. Edge: 196.5MB. GIMP: 244.8MB. OS memory usage remained relatively flat once app exited. xUbuntu 20.04.
I think Discord implemented some measures to guard against those files and Chromium was patched to mitigate this (which is why Edge and Vivaldi are fine), so it's not surprising that something like Safari might struggle with Evil GIFs under certain circumstances as well.
Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak
#178Earlier quoted context omitted.
I still don't see how this can be classed as a bug by anyone other than apple. You have a single case of 10% lifetime usage (plus a 20% one you mention), along with thousands of reports of people with 2-5% - which you also stated was too high - based on your insistence of using TBW (which can vary by up to 10000x depending on the tech) instead of percentage used (supplied by the manufacturer). I had an out of memory…
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…
Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak
#179Earlier quoted context omitted.
> Apple is pretty good at the planned obsolescence game Nah, they suck at it. My GF is just finishing her bachelors thesis in the living room on my 2013 MBP with 4 GB RAM. First battery, updated all the way from Mavericks to Big Sur. Still supported, still useful and prettier than 80 % machines out there.
You're right. Macs have excellent build quality and are durable as hell. Planned obsolescence with Apple is seen more with iPhones. There was the recent story about Apple slowing down older iPhones via software updates [1] [1]: [ https://www.bbc.com/news/technology-51413724 ]
The lack of communication was a problem but "planned obsolescence" in this case is just tin-foil hat nonsense.
Re: Animated GIF uses over 35GB RAM in Acorn on M1 Mac, likely due to memory leak
#180Earlier quoted context omitted.
Browsers and other players will generally be fine, as they render the image progressively. However, editors /processing tools which attempt to load it as a series of frames or a video will usually break, as memory consumption explodes, unless they have a smart disk buffer system to handle it. I wouldn't be surprised if some poorly implemented players were built on top of abstraction layers that end up flattening the…
And this kids, is why we have key and delta frames. We should drop gif support.