MS Teams Helper using up >100% of CPU MacBook

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.

Second that question. My 2017 MacBook Pro gets burning hot whenever I use MS Teams app, which I'm using daily for work. Very interested in the answer to this question.

Same issue here:

2015 Macbook Pro (Retina) 2.7 GHz Dual-Core Intel Core i5. macOS Catalina

Intel 1536 MB Teams 1.3.00.18164.

Off Video-Call

On Video-call

*Not shown on screen %GPU showing 0.7

On Video-Call (Graphics acceleration OFF)

Same for me.

Interestingly it was fine yesterday before I chose the 'open in a new window' feature, though this in itself didn't seem to perform an upgrade:

You have Microsoft Teams Version 1.3.00.18164. It was last updated on 24/08/2020.

I'm having this exact same issue, coupled with not being able to share my screen and audio hanging. 

Also having these issues :)

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.

I too have been having the high cpu usage really over the last couple of weeks.  The teams thick client has been pretty much useless on my mac (2018) during this time.  Web client is hit or miss.  I was able to install one of our enterprise monitoring tools on the web client and found that MS is likely having a really rough time trying to figure out what to do because everything points to the client (browser) taking all of the time lag.  The server side of the transaction is very fast.  Unless they start using some kind of javascript injection based tool for the web client, that one will be DOA.