I have noticed in the last couple weeks that "Teamviewer_Service" is using excessive CPU resources (often over 100%). This is version 14.2.8352 for Mac. It is noted on latest version of Mohave, as well as High Sierra. I have seen this on three different machines. These are machines that are just running Teamviewer, and are not active in screen sharing. It seems to take awhile before this behavior is noted, so it doesn't happen right away after startup.
I've got the same problem on my MacBook Pro 8,2 (Sierra).
The cpu load is so high, it takes a minute before the client connects to the Teamviewer servers. Whats going on there? Doesn't noticed anybody from the Teamviewer Developers this terrific bug?
By the way the v13.2 Version of Teamviewer works as expexted ... unfortunately this one can't connect to the target systems which are on a higher version. ;-(
I too have exactly the same problem with causing my Mac to burn up due to extreme high CPU usage with the latest 14.2.8352 on MacOS Sierra.
I need then force quit Teamviewer and restart the application. Then after a while, the process would be there eating up CPU again. I'm scared to keep Teamviewer running now as It is detrimental both to my Mac's longevity and battery life.
Why hasn't Teamviewer look into this problem?
Same issue as well. I can always tell its happening since Macbook fans will start spinning up to high. I leave the application open most of the day, even if not connecting to a client and it seems to spike after its been open for a bit. Closing application and restarting it works but always comes back. I havent seen this issue prior to the update to version 14.
Same here, excessive CPU loading, up to 400+ %.
However, when running TeamViewer inside a Windows 10 VM on top of MacOS it works fine. There's clearly a problem with the Mac version of TeamViewer 14!
MacOS Mojave 10.14.5
MacBook Pro i7/16G
I have this problem before, but i found that, after unplugged the hdmi external display, everything back to normal.
Try to see if this can help.
Thanks for the hint but i never had or will have an external monitor via hdmi in use ... so the problem must have other triggers ...
Furthermore it is very unlikely that all the mac users with different os and hardware have an external monitor attached !