MS Teams Helper using up >100% of CPU MacBook

Hi Dr JPH,

We have noticed this issue Microsoft Team Helper takes certain amount of CPU for mac, we will continue investigating this issue and seeking help for our related team.

Once we get any information, we will let you know as soon as possible. Current if it is acceptable, we would like to suggest using the Teams web, which you can login through http://teams.microsoft.com/ 

Let me know if you still need any assistance.

Yours Sincerely,

George

Hi Mr Xu,

Having 2 mac , one is using high CPU ressources when Teams is launched, the other not. The second one uses a previous version, the 1.00.309271. So, i've copied the previous version in the other mac, and then it's ok on both of my macs.

Maybe the Microsoft team should compare the version 1.00.309271 with the last one to find out what's going wrong?

Til this time, and if i'm right, could Microsoft give access to older version to download it ?

Regards

LC

My solution was to quit my job. I don't have use Teams anymore. Suddenly my problems are gone.

Your milage may vary.

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!

Apologies in advance for the me too nature of this reply.

I'm facing similar issues of a MackBook Pro 13'' 2020 that is well speced: Microsoft Teams Helper grabs the %CPU and also %GPU. So I'm afraid it's taxing the laptop both way thus pushing fans to go full speed.

This translates into an awful user experience and taking into account that MS Teams is used in my organisation as the corporate tool for communications it reflects poorly on Microsoft and their comms solution.

Hoping for a fix in the near future.

Great, thanks for the reply. The web app is fine as a stop gap, but can you provide a timeline for resolving this issue?