High CPU/GPU/Power usage
For some reason the latest update has Teams using between 8% and 25% CPU idling, doing nothing. There is an issue with this update.
Joining a video on teams on my MacBook Pro is an absolute battery killer. I can get between 60 - 90 mins tops before I run out of power.
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 ?
Sven Jansen commented
Teams converts my high end Business Ultrabook to a coffee heater. Idle Teams takes around 20-25% CPU and draws lots of battery.
41% of the battery is used up on teams
Since some update the application utilizes CPU a lot also when idle! When I'm on battery it is a disaster!!!
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
Teams : Using too much memory and CPU capacity. We have upgraded our machine
on the 1809 version and with Teams version as 1.2.00.8864 but
still high memory utilization is being observed.
Teams using too much memory while initiating calls
Teams using too much memory in surface pro’s and it is causing application freezes intermittently-
Teams in Surface Hub functionality – Although the Teams application is working with Surface Hubs, issues like intermittent sound distortion, call connectivity issues are reported. The same works fine when using skype-
Reese Stanley commented
I can typically keep the client open without issue - the battery drain isn't ideal, but it isn't crippling either. The real problem comes during online meetings **especially** when I'm sharing my screen. My MacBook went from ~80% to putting itself to sleep over an hour and a half when I usually get a solid 6-7 hours otherwise.
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%.
Phillip Demro commented
1.1 GB of RAM and 26% of CPU after 3 hour idle? THe performance is horrible. Focus on resource management or nobody will adopt
bella johsan commented
Laptop bettery is a serious issue in this time regarding this i found your post really helpful for all.If someone have a problem related to lenovo laptop and desktop and have any query related to this then take help from this site https://www.lenovosupportphonenumber.com/blog/fix-lenovo-error-code-0xc0000185/
Emma Watsun commented
Read this blog on the topic Dell Laptop Not Charging, I am sure you will get your solution from this blog. I had also the similar issue and through this blog I have resolved my issue. You can read the blog from following link-: https://www.delltechsupportnumbers.com/blog/simple-steps-fix-dell-laptop-not-charging/
This is such an interesting blog. I'm really impressed by the manner in which you have organized content in it. Laptop batteries are one of the important issues in the laptops. If anyone wants to know more about Antivirus can contact https://avastsupportnumber.co.uk/blog/fix-avast-error-7005/ for get instant.
A year later and this still is a problem. Teams is the single great battery drainer on my macbook. And closing it means I'm not reachable for communication.
Artem Makaryan commented
something has changed or still the same? id like to know does the developers are working on optimisation or for functionality only.
I can confirm the same behaviour on client 10.0.16299.492 x64, Teams version 1.1.00.17553.
On a system with 26 days uptime, instances of teams.exe have collectively written 340GB of data and read 550GB.
This is pretty abhorrent
Michael Lerro commented
My computer uptime is 1 week, and your Teams electron app has been running the whole time. In that week 3 Teams processes have cumulatively done:
* over 12 hours of CPU Time (on a quad core i5-7600K)
* using 1.2 GB of RAM
* 312GB of IO reads (!!!)
* 280GB of IO writes (! what?!)
Attached is a screenshot of my Task Manager. Again, this was in a single week (at most) of usage.
I have an i5-7600K, running Windows 10 build 1709 (16299.492) with latest updates.
According to Teams I'm running version 1.1.00.17553 (64-bit). It was last updated on 7/3/18.
I've got memory dumps of the offending processes available on request (the form submit here doesn't like the 370MB file).