High CPU Usage Continues after Ending Video Call

Question

Edit 2: I'm running the latest teams-insiders build (1.3.00.16851) which was released June 17, 2020 and the problem seems to have gone away. I've been on several video calls today - which all included screen sharing and the CPU usage has returned to normal afterwards! Hopefully these fixes get incorporated into the non "insiders" builds.

Edit: the problem (for me) only occurs on a call after I share my screen. If I am just using my camera the CPU usage remains normal. Hopefully this helps troubleshoot the issue.
Update: I was mistaken, problem still exists.

Hello All,

I've noticed after completing a video call in Teams that the CPU usage remains high. The only way to get the CPU usage to return to normal is to close Teams completely, and then reopen it again.

I'm running on Ubuntu 20.04.

If I had to guess the process that's spawned for the video call is never terminated, despite the call ending.

Answer 1

I have the same issue on ubuntu 18.04 with the HWE kernel installed. The problem seems to be related to outgoing video encoding. I have GPU acceleration turned off in settings.

This is top output during a presentation (no camera or screen sharing on my side):

  PID PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 8600 20   0 3286152 220384 110176 R  13.2  1.4   3:51.36  `- /usr/share/teams/teams                                  
 8602 20   0  374908  37748  31684 S   0.0  0.2   0:00.04      `- /usr/share/teams/teams --type=zygote --no-sandbox   
 8662 20   0 1516688  85212  62412 S   0.0  0.5   0:00.42          `- /usr/share/teams/teams --type=renderer --autop+ 
 8708 20   0 2677608 549072 103584 S   8.9  3.4   4:04.40          `- /usr/share/teams/teams --type=renderer --autop+ 
 8735 20   0 3244900 200928  97672 S  27.8  1.2   8:56.15          `- /usr/share/teams/teams --type=renderer --autop+ 
 8640 20   0  754732  63184  41120 S   0.0  0.4   0:00.16      `- /usr/share/teams/teams --type=gpu-process --enable+ 
 8644 20   0  445924  13088   2404 S   0.0  0.1   0:00.00          `- /usr/share/teams/teams --type=-broker

After the presentation was over, CPU usage returned to normal:

  PID PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
 8600 20   0 3276280 218800 104424 S   0.7  1.3  10:09.41  `- /usr/share/teams/teams                                  
 8602 20   0  374908  37748  31684 S   0.0  0.2   0:00.05      `- /usr/share/teams/teams --type=zygote --no-sandbox   
 8662 20   0 1516688  85212  62412 S   0.0  0.5   0:00.48          `- /usr/share/teams/teams --type=renderer --autop+ 
 8708 20   0 2800984 534408  82556 S   0.3  3.3   8:57.81          `- /usr/share/teams/teams --type=renderer --autop+ 
 8735 20   0 3255800 202172  92552 S   0.0  1.2  21:38.26          `- /usr/share/teams/teams --type=renderer --autop+ 
 8640 20   0  754732  63184  41120 S   0.0  0.4   0:00.20      `- /usr/share/teams/teams --type=gpu-process --enable+ 
 8644 20   0  445924  13088   2404 S   0.0  0.1   0:00.00          `- /usr/share/teams/teams --type=-broker           

After a call in which I shared my screen (no camera):

  PID PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                     
 8600 20   0 3285868 240556 111648 S   0.0  1.5  11:10.69  `- /usr/share/teams/teams                                  
 8602 20   0  374908  37748  31684 S   0.0  0.2   0:00.06      `- /usr/share/teams/teams --type=zygote --no-sandbox   
 8662 20   0 1525316  85508  65576 S   0.0  0.5   0:00.71          `- /usr/share/teams/teams --type=renderer --autop+ 
 8708 20   0 2869044 585888  88236 S   1.3  3.6  11:31.37          `- /usr/share/teams/teams --type=renderer --autop+ 
 8735 20   0 3254500 230964  93000 S 104.3  1.4  41:53.41          `- /usr/share/teams/teams --type=renderer --autop+ 
 8640 20   0  754732  63184  41120 S   0.0  0.4   0:00.28      `- /usr/share/teams/teams --type=gpu-process --enable+ 
 8644 20   0  445924  13088   2404 S   0.0  0.1   0:00.00          `- /usr/share/teams/teams --type=-broker           

uname -a:

Linux ********** 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Answer 2

Confirming this happens on Fedora 31

Linux [redacted] 5.5.11-200.fc31.x86_64 #1 SMP Mon Mar 23 17:32:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Answer 3

I can confirm this behaviour:

OS: PopOS (Ubuntu 19.10) with GNOME 3.34.2
Teams Version: 1.3.00.5153 (64 bit).
I do not have Skype installed nor do I have a ~/.config/skypeforlinux directory

The only fix I have found to date is to restart the teams client:

Kernel:
5.3.0-7642-generic #34~1584408018~19.10~21df4b1-Ubuntu SMP Tue Mar 17 13:38:51 UTC x86_64 x86_64 x86_64 GNU/Linux

Answer 4

It is intentional, they want us off Linux and go back to Windows. Everybody is working from home, it is a great way to force people because they need to communicate with their colleagues who are using proprietary crap like Skype, Zoom and Teams. With Skype and Zoom I experience the same issue. (Zoom could be unrelated of course...)

Answer 5

Same issue with me, ubuntu 18.04.03
CPU 100%