[rnestler]

Thanks for the link. The issue seems to be the IOAccelerator framework:

> I’ve narrowed it down quite a bit (and submitted it to Apple as FB9112835).

> What’s going on is that the IOAccelerator framework has some sort of massive leak in it, where it’s using up 35GB of ram, 25 of which is going to swap (which is why you’re seeing kernel_task flake out).

> On intel, the same image only uses 1480K from IOAccelerator.

[SXX]

Wow. This can explain some of excesive swap usage on M1.

[saagarjha]

Seems like a poor conclusion to draw with this little information.

[zarzavat]

People have reported their SSDs filling up (in terms of total writes) much faster on Apple Silicon machines. If IOAccelerator can leak like this then it would definitely explain it. 25GB swap for one image is absurd. Multiply that by a few months of usage. It may not be a smoking gun but it is a fingerprint in the pool of blood.

[MintPaw]

If this were the cause people would have noticed having 0% free memory way before their SSDs started dying.

[valuearb]

That’s been debunked.

[fouric]

It hasn't been debunked if there's no source for the claim...

[floatingatoll]

Apple said that the kernel interface used by smartctl is emitting invalid data, which invalidates all conclusions drawn from it, such as “there is/isn’t a problem with SSD wear”.

[smhenderson]

Perhaps, but if you read the Twitter thread others are suggesting the same thing and people seem excited/happy that there is possibly a potential fix that may come from Gus discovering this.

So, maybe premature to get too hopeful but certainly not too soon to look in that direction?

[saagarjha]

People are suggesting the same thing because it sounds nice to be able to correlate them, but the evidence just does not exist yet. At the moment is seems somewhat likely that they are correlated at all, really.

[lillecarl]

And yet it's relatively performant, says a bit about the quality of components in apple hardware (SSD in this case)!

[NobodyNada]

Note that IOAccelerator memory usage doesn’t necessarily mean a bug in IOAccelerator. If my memory is correct, when an app allocates buffers for hardware-accelerated graphics, that memory is attributed to IOAccelerator. So it’s still likely to be a bug in some system framework that’s allocating all these buffers (especially since we only see the issue on one platform) — but an application bug is still a possibility.