Has anyone else noticed FaceTime (audio) leaking massive amounts of memory on macOS Sierra?
This is what happens when I start FaceTime call from my Mac (13 rMBP):
1. Facetime call starts with the avconferenced process using around 80MB of ram (around the same amount it uses while idle).
2. The avconferenced process slowly eats more ram at a rate of about 5-10MB every few minutes.
3. By the end of a long call I've seen ram usage for avconferenced as high as 3GB of physical memory plus an additional 2-3GB of compressed memory.
4. Obviously the longer a call goes on the worse performance (of both the call and my system) becomes (particularly on my 13 rMBP) as my memory pressure is slowly pushed into the yellow and eventually the red.
5. Ending and restarting the call "resets" the ram usage, but doesn't fix the underlying issue.
I know at least one other friend who experiences this on his iMac (2011) and 15 rMBP (2016), both running macOS Sierra. I should note that I never experienced this on my previous Retina iMac (2014), but given that I had 24GB of ram I may have just never noticed... I haven't tried this on my current desktop (i5 Hackintosh with 16GB of ram), but I imagine that results would be similar to my friends rMBP.
Has anyone else experienced this? Is this a known issue (I've searched for it both here and on google and came up empty handed)? Does anyone have any tips for fixing this? Should I go ahead and file a bug report with Apple?
This is what happens when I start FaceTime call from my Mac (13 rMBP):
1. Facetime call starts with the avconferenced process using around 80MB of ram (around the same amount it uses while idle).
2. The avconferenced process slowly eats more ram at a rate of about 5-10MB every few minutes.
3. By the end of a long call I've seen ram usage for avconferenced as high as 3GB of physical memory plus an additional 2-3GB of compressed memory.
4. Obviously the longer a call goes on the worse performance (of both the call and my system) becomes (particularly on my 13 rMBP) as my memory pressure is slowly pushed into the yellow and eventually the red.
5. Ending and restarting the call "resets" the ram usage, but doesn't fix the underlying issue.
I know at least one other friend who experiences this on his iMac (2011) and 15 rMBP (2016), both running macOS Sierra. I should note that I never experienced this on my previous Retina iMac (2014), but given that I had 24GB of ram I may have just never noticed... I haven't tried this on my current desktop (i5 Hackintosh with 16GB of ram), but I imagine that results would be similar to my friends rMBP.
Has anyone else experienced this? Is this a known issue (I've searched for it both here and on google and came up empty handed)? Does anyone have any tips for fixing this? Should I go ahead and file a bug report with Apple?