Extreme CPU usage of Teams for Mac when using video
Teams for Mac makes the computer almost unusable when using video conference. CPU goes to 100%, teams app slows down, Mac starts fan at max speed making even worse the experience of participating in a video conference (because of the noise).
A fix is URGENT and IMPORTANT, over any other feature.
Surely this is because Teams is an Electron app, which are known to be very resource hungry. 100% CPU happens on PCs too. Teams has fried at least four of our Surface Pros (they can't cope with the heat and the GPU seems to die).
Teams app becomes completely UNUSABLE when video or desktop sharing is active for me, pegging CPU and causing severe unresponsive behavior to Teams and other apps. I have tried shutting everything down except Teams and the problem persists. This issue has been happening for a long time - please make this a top priority to fix. Voted.
Ingo N commented
I am using a MBP 2020 (i7, 32GB). When I jump on a call with video enabled, my Mac becomes unresponsive latest after 15 minutes. The Teams app starts flickering, CPU usage goes up to 160%. My Mac is so unresponsive that I cannot even edit an Excel sheet while sharing my screen. This is absolutely ridiculous! I need MS Teams to work with my customers on a professional level - MS Teams makes it impossible to do so!
absolutely hammering the CPU. My mac with i7, 16GB becomes unusable when I jump on a video call since the last update Version 1.4.00.16567
Ken Snyder commented
Yes! My computer becomes unresponsive on any teams meeting. I have 2020 8 core i9 MBP and total CPU hovers at 1350%. If I click mute/unmute it takes around 3 seconds to take effect.
Compare to Zoom that uses around 35% CPU on just one core.
Possibly related is all participant videos and shared screens flicker on and off. So bad that I can't look at anyone. So then it becomes an audio conference.
this really needs to be sorted, it makes my laptop so loud when I am on meetings, its like when im exporting HD video or something lol for a video call with a couple people, Microsoft really don't care about the performance issues with this app at all it seems, are you actually ever going to listen to your users?
Oh my goodness. The Teams app for macOS is so inefficient. My battery and also the installations at my customers... they report the same problem. It's just a disaster.
Sylvain Goletto commented
When in video with Teams on MacBookPro (4 cores) turbo boost is not triggered and unable to use Teams or other apps. (this was not the case few months ago, I use teams on Mac since more than 2 years now)
Unable to open a Teams chat, open a channel, share a Teams document. Each click takes 10 to 30 sec to be executed. UNUSABLE !
wonder if they will ever actually pay attention to this issue and sort it out...
2020 8 core i9 MBP and whatever codec they're using for video in teams just outright destroys it. Feels like I'm building Windows 10 from source every time I have a video meeting.
Does not happen with any of the other video apps I use: Hangouts, Slack, Zoom, Skype. So is definitely fixable if given adequate attention.
Geraldine Bragg commented
For me, this problem was also very relevant. For example, in conferences at lectures, but we made the decision to turn off the camera when it is not necessary. But still, I would like everything to work well with video communication.
this issue is also on windows, whenever I search it there's literally 1000s of people over the space of the last 3 or so years talking about these issues. I doubt it is ever getting fixed...
Ben BROECKX commented
Same problem, only when in video call, on MacBook Air M1 16GB. This is a new issue.
André Meyerjürgens commented
I have the same problem. I have seen in intel power gadget (https://software.intel.com/content/www/us/en/develop/articles/intel-power-gadget.html#attachment-heading) that in case i am in a teams video call / conference, requested CPU frequence will be throttled from turbo boosted 4 GHz down to ~ 2 GHz. During the call all other applications and teams of course too have a really bad performance. Directly after leaving the call, the CPU frequence boosts back up to 4 GHz and the system performance ist normal again. All in all you can say, attending a teams video call will throttle overall CPU performance to half and teams itself uses a quarter of remaining CPU ressources.
What can i so, that Intel Turbo Boost will mit be throttled by teams?
Also experiencing similar issues, while running Teams on iPad (Air and Pro) works flawlessly. Will the M1 Mac finally solve this behaviour?
Juan T commented
MacBook Air (Retina, 13-inch, 2019) and teams cripple it. can you guys make this software work as expected? I know my company has asked you about it but when will you do something..
Just to echo the previous comments, this is a big deal and should have been fixed years ago. Ridiculous amounts of CPU/power usage. I have tried updates and no change. Sometimes it's a little better, sometimes it's a lot worse. I am also on 1.3.00.24758 so the updates are clearly not fixing the problem
Jonathan Sanderson commented
The developer preview helps a little for me, but I'm still seeing extreme CPU use and reduced frame rate in multiparty chats. Reducing the meeting window size helps the frame rate, which seems odd.
I am forced to use Teams for my job (1.3.00.24758). Anytime I try to do a teams video conference using the Mac Desktop, 90-100% or more of my CPU is used, the video and the app itself becomes laggy and completely unusable to the point where I cannot even type messages in Chat and my cooling fan is blaring. I'm worried the heat is damaging my computer and the app keeps freezing. Force Quitting doesn't work and I end up having to forcibly shutdown and restart my computer several times a day. This is literally a brand new maxed out 2019 MacBook Pro, 2.4 GHz 8-Core Intel Core i9 with 64GB 2667 MHz DDR4 and AMD Radeon Pro 5600M 8GB Intel UHD Graphics 630 1536 MP.
Patrick Gidich commented
THIS FIX SHOULD WORK
(use the developer preview)
It will move you to Teams Version 1.3.00.18164 (developer preview) or later which apparently has the resolution to the issue (thanks Microsoft!)