MS Teams Helper using up >100% of CPU MacBook

Anonymous

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.

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

218 answers

Anonymous

2022-10-25T08:39:34+00:00
Okay, I found a solution on my Mac (16'' 2021 M1 Max, Monterey).

Mouse: Roccat Kone EMP (wired)

Solution first:

sudo mv "/Applications/Microsoft Teams.app/Contents/Resources/app.asar.unpacked/node_modules/media-hid/build/Release/media-hid.node" "/Applications/Microsoft Teams.app/Contents/Resources/app.asar.unpacked/node_modules/media-hid/build/Release/media-hid.node.bak"

Debugging steps:

When opening teams without the Mouse everything worked normal, joining a call was no problem.

As soon as the mouse was involved (USB-HUB or direct) CPU usage skyrockets.

Specifically: the presence of the mouse is not affecting teams. But as soon as you move it the CPU usage skyrockets. For that effect the mouse does not have to hover over the window btw., just moving it some pixels on another screen is enough.

Edit: CPU skyrocketing means that one of the "Renderer" processes increases to 50%-100% initially and then stays at ~50% forever. Which points at some continuous loop keep the system busy. So the mouse movement "changes" something in the process, it does not calm down after some seconds.

After finally having a simple test to see the behavior I took process dumps before and after; and you could visually spot the difference immediately.

The following block caught my attention:
```
+                                     2174 __IOHIDDeviceInputReportWithTimeStampCallback  (in IOKit) + 140  [0x19db8b608]
    +                                       2174 CFSetApplyFunction  (in CoreFoundation) + 328  [0x19b11f5cc]
    +                                         2174 CFBasicHashApply  (in CoreFoundation) + 148  [0x19b11f688]
    +                                           2174 __CFSetApplyFunction_block_invoke  (in CoreFoundation) + 28  [0x19b11f860]
    +                                             2174 __IOHIDDeviceInputReportApplier  (in IOKit) + 72  [0x19db8b718]
    +                                               2173 hid::DeviceImpl::reportCallback(int, void*, IOHIDReportType, unsigned int, unsigned char*, long)  (in media-hid.node) + 48  [0x113619140]
    +                                               ! 2166 hid::DeviceImpl::modifiedElementsWithReportID(unsigned int)  (in media-hid.node) + 32  [0x113619550]
    +                                               ! : 1422 hid::DeviceImpl::elementsWithReportID(unsigned int)  (in media-hid.node) + 100  [0x113619628]
    +                                               ! : | 1411 hid::DeviceImpl::CopyElementsUsingFilter(__CFDictionary const*, std::__1::vector<hid::OSElement<__IOHIDElement*>, std::__1::allocator<hid::OSElement<__IOHIDElement*> > >&)  (in media-hid.node) + 52  [0x1136196e4]
    +                                               ! : | + 1410 IOHIDDeviceCopyMatchingElements  (in IOKit) + 60  [0x19db88dbc]
```
After some digging around I figured that the block references "media-hid.node" which is found in the Teams folder. In a desperate attempt I renamed it so that Teams cannot load it, and to my surprise Teams does still start.

It seems that some outer error handling is not considering that library vital (yay!).

Thanks to the previous poster hinting at the gaming mouse, I would have never even remotely thought about that!
Was this answer helpful?

20+ people found this answer helpful.

0 comments No comments
Anonymous

2022-12-09T13:46:54+00:00

Hi,

thanks for this.

I had the same issue and renaming the file solved the issue.

Would really be great if there'd be an official fix for that, instead of manipulating the teams installation.

Regards
Was this answer helpful?

0 comments No comments
Anonymous

2022-12-09T14:04:29+00:00

I renamed my teams to slack.exe and is working better now.
Was this answer helpful?

5 people found this answer helpful.

0 comments No comments
Anonymous

2023-01-10T10:24:33+00:00

Almost 3 years this issue keeps happening ... I'm using the latest version of Os X and Teams ...
Was this answer helpful?

7 people found this answer helpful.

0 comments No comments
Anonymous

2023-02-13T13:30:24+00:00

i had to unplug my Roccat mouse to be able to work. is there any fix?
Was this answer helpful?

0 comments No comments