Jakob Theiner

My feedback

  1. 78 votes
    Sign in
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    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).
    Fix this!

    Jakob Theiner supported this idea  · 

Feedback and Knowledge Base