91–100 of 342 posts
Earlier quoted context omitted.
No. There is no way this has anything to do with that. That's an issue with the OS swapper algorithm, and it should be fixed in macOS 11.4 according to reports.
Selling M1s with a decent amount of RAM would surely help too
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.
Earlier quoted context omitted.
It would be very bad if OS memory usage did not return to flat no?
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,…
Earlier quoted context omitted.
Several programs including Firefox Nightly have been reported to blow up, so no it's not limited to a "specific program".
If you're actually following it proves exactly what I'm saying, the gif has nothing to do with it, Firefox isn't blowing up opening that gif, it's hitting whatever framework leak exists. This is like saying "DOCX bluescreens Windows" (which implies something that could possibly be exploited in some pretty scary ways) when in reality Word just happens to make some syscall that bluescreens Windows no matter who calls i…
The person reporting is the author of a graphics editor, he damn well knows the difference between a bug in his own editor and system frameworks. The issue seems to be with opening the GIF via default system frameworks, not anything special the editor is doing. Chances are it will affect any other programs using the same frameworks, maybe even GIF viewers.
Earlier 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.
Just out of interest, is she still using the same HDD? I find that the performance of older MacBooks are pretty awful under recent version of Mac OS if the storage hardware is the older non-SSD drives. My old $work MacBook with a HDD was thankfully swapped out for a SSD version -- the difference was night and day. Though this SSD machine is starting to slow down noticeably with Big Sur...
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,…
If you close the app the OS should clean up the memory no matter what the app was doing
Earlier quoted context omitted.
The framework is part of Apple’s UI stack and indicates a window system/graphics driver bug somewhere in macOS. So it’s probably more than just “an application has a bug”, but still not very interesting until we learn more.
My point was nowhere nearly as interesting as if a specially crafted gif somehow triggered a memory leak in a driver when rendered. The title doesn't make it clear individually opening 730 frames in an the editor is the userspace action exposing an underlying system bug
Earlier quoted context omitted.
Selling M1s with a decent amount of RAM would surely help too
The iPad Pro has 4GB with almost the same CPU and is absolutely snappy editing 4K videos, instantly switching in and out of apps etc. It’s a matter of software architecture and not raw space available.
Earlier quoted context omitted.
It's a real issue affecting a small minority of users; I have one who has already gone through 20% of their SSD lifetime writes. Here's one of the worse ones back in February: https://twitter.com/marcan42/status/1361847686417190918?s=19 11.4 is in beta so not many people are using it, but at least one of the folks with the issue is running it and said it improved things. Apple were definitely made aware of it, hence…
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…
See also: https://eclecticlight.co/2021/05/17/how-m1-macs-feel-faster-...