Additional features, settings, or issues not covered by specific Microsoft Teams categories
Same issue here with 1.5.00.8073. (MacBook Pro (Retina, 15-inch))
--->> Fully unable to use the TEAMS UI when in a meeting, like unmuting your mic (!)
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Since the latest update of MS Teams (current version 1.3.00.9271 updated on 07/05/20) on a MacBook (early 2015), every time I now join a Teams call, the Microsoft Teams Helper is using >100% of CPU and causing the laptop to overheat. I have disabled the GPU acceleration as seen on some other message boards but this has no impact, and could do with a fix for this ASAP.
Many thanks in advance.
Additional features, settings, or issues not covered by specific Microsoft Teams categories
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Same issue here with 1.5.00.8073. (MacBook Pro (Retina, 15-inch))
--->> Fully unable to use the TEAMS UI when in a meeting, like unmuting your mic (!)
Same Problem.
Macbook Pro 2019, 16 GB Ram, 2,3 GHz 8-Core Intel Core i9.
Software up to date.
Teams Heavy user and my ventilator never stops running on teams calls.
Teams app on MacOS has never been snappy, but with version 1.5.00.8073, definitely seems like there is some kind of regression. I see the app's two processes each consistently taking 60-80% CPU, and being very slow to respond to keystrokes. Especially noticeable when I'm in a Zoom call.
Guys, I found a relatively good workaround. I'm using now the https://webcatalog.io application. In this application, you can run every web-application like a standalone app. It is a free tool (up to 10 apps). It does also sandbox the related web app. Since Teams is also having a webapp, it can be used inside webcatalog. The look and feel is almost identical and the CPU issues are gone. Give it a try :-)
Two years later, is there still not a fix for this?