Teams using a lot of CPU - reduce idle power
For some reason the latest update has Teams using between 8% and 25% CPU idling, doing nothing. There is an issue with this update.
Jakob Theiner commented
This issue still persists! How can this be? I'm a software developer myself, if I were to check in code that does that I would be strangled by my customers.
I have an Intel Core i7 with six cores/12 threads. Teams pushes one thread to the max, causing the CPU's turbo to max out. In effect using ~16% of a pretty potent CPU. This happens after some time when Teams was minimized. As soon as I open it up the issue "disappears" - as in gets less worrysome. The CPU load drops to ~3%. Which in my opinion is still far too much for a chat client.
Cut the **** Microsoft! I love Teams, it's really a great tool, but bugs like this shouldn't make it through QA. Well this happens, I guess. But your even customers have been complaining about this issue for over a year and still nothing? This is unacceptable!
Our users were getting annoyed by the noise a fully ramped up Laptop makes and since they found out it was Teams they close the app. Now that's not very helpful to have a chat client which should be used to improve communication but gets shut down by users (rightfully so).
Robert Slaney commented
Teams Version 1.2.00.19260
Same thing happened when I resumed from hybernation. Opening the app from the tray iocn seems to clear the synchonization state and the CPU when back to normal. Maybe there's a UI threading issue here ?
Andres S commented
Hi, well, same here. I started noticing my laptop going full wind blast mode for no reason and traced it to Teams using 100% (of one CPU thread).
In my laptop's case, that is 12.5% (100% CPU / 4 cores / 2 threads per core = 1 thread running at 100%).
Going over its execution details on Process Explorer, found that there is one thread which starts at "IsSandboxedProcess+somenumber" and that thread is stuck on "waiting thread sync". That thread had used *a lot* of CPU Process Explorer claims.
So, this process is stuck on a deadlock situation of sorts, my very rusty developer gut tells me. If that is the case, thats a crass bug.
Once quit Teams (using its own Quit command), the wind turbine mode on my laptop stopped, almost immediately.
Once I started Teams, it didn't go CPU crazy. My laptop had just resumed from sleep.
I have no more time to delve deeper into this, hopefully this information helps - somehow. Teams is quite slow, but now being CPU hog... not good.
I will cross post this on other threads I find relevants, apologies in advance.
leafblower....lol good description.
Still having this problem. I run a I7 (8 cores) en 32GB ram, but when ever I keep Teams running in the backgroud (or foreground) my CPU is like a leafblower and it consumes a lot of my CPU, dropping my battery. Needs to be fixed
This is exactly what I'm experiencing on all my company Macs, ~30 total. CPU spikes on one of the three existing helper processes in Teams when I'm typing. This happens on MacBook Airs and Pros on all different versions High Sierra and Mojave. Basic CPU is around 2-6% which is already too high. Then when we start typing it shoots up to ~60%.
I see the same behaviour. In fact, when Teams is running Outlook spikes CPU utilization as well.
We experience this also in the MacOS- environment. Optimalisation is very welcome.