MS Teams Helper using up >100% of CPU MacBook

Anonymous
2020-05-22T10:17:30+00:00

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.

Microsoft Teams | Microsoft Teams for business | Other

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.

0 comments No comments

218 answers

Sort by: Most helpful
  1. Anonymous
    2023-02-23T14:03:58+00:00

    its 2023 and i still have the same problem (macbook air m1)

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-07-26T19:04:24+00:00

    I wrote a bash script along with 'cpulimit' via Homebrew to stop it from overusing CPUs. Had to do the same for OneDrive. while it does slow MS teams down a bit, my mac remains usable. YMMV

    #!/bin/bash
    while [[ 1 ]]; do
    clear
    date
    cpulimitpids=ps auxm | egrep -v "grep" | egrep cpulimit | egrep "pid=" | tr -s " \t" "\t" | cut -f 15 | tr -s "=" "\t" | cut -f2

    echo OneDrive:  
    uppercasename=ONEDRIVE  
    apppids=`ps auxm | egrep OneDrive | egrep -v grep | egrep -v "File Provider|FinderSync" | tr -s " \t" "\t" | cut -f2 | sort -n`  
    for apppid in ${apppids[@]}; do  
         FOUND=`echo $cpulimitpids | tr " " "\n" | egrep "^$apppid\$" | wc -l`  
        if [[ "$FOUND" -eq "0" ]]; then  
            cpulimit --limit=100 --lazy --include-children --pid=$apppid &  
        fi  
        echo ${uppercasename}:  $apppid  Found:  $FOUND  
    done  
    
    echo Teams:  
    uppercasename=TEAMS  
    apppids=`ps auxm | egrep 'Microsoft Teams Helper' | egrep -v GPU | tr -s " \t" "\t" | cut -f2 | sort -n`  
    for apppid in ${apppids[@]}; do  
        FOUND=`echo $cpulimitpids | tr " " "\n" | egrep "^$apppid\$" | wc -l`  
        if [[ "$FOUND" -eq "0" ]]; then  
           cpulimit --limit=100 --lazy --include-children --pid=$apppid &  
        fi  
        echo ${uppercasename}:  $apppid  Found:  $FOUND  
    done  
    sleep 60  
    

    done

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-07-06T08:41:06+00:00

    the problem is THEY DON'T CARE what benefit is it to them to sort it.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-05-16T08:37:52+00:00

    People - I found the bug and some kind of a solution with the help of seo-praxis.de

    Main question: If you are joining a teams meeting, your pc is getting very loud, and slow?

    Question 1: Do you use Teams MacOS App?

    Question 2: Do you use external screens?

    Then the solution might be working for you as well.

    Step 1: Go into an empty meeting/test with a friend & close all other Apps beside Teams.

    Step 2: Open "Activity Monitor" and watch CPU usage.

    Step 3: Wait until the mac CPU usage is getting high (>50%)

    Step 4: Don't get angry.

    Step 5: Disconnect all external monitors.

    Step 6: Wait 1-3minutes (it sometimes takes a while).

    Step 7: Your mac should now be down to <20% CPU usage and you can have the meeting normally.

    Since the Team around Teams is obviously not able to fix this bug since 2 years..

    at least the solution will enable you to take part in meetings again.

    Thanks goes to Technical SEO Agency from Freiburg Breisgau seo-praxis.de

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-07-27T07:04:55+00:00

    Hi,

    Any update on this? 

    My mac is on fire every time I use MSTeams for call.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments