macOS repeating Console system logs while TeamViewer app is closed

mz1
mz1 Posts: 3
edited May 2023 in General questions


TeamViewer app is closed. Yet, the Console reports the following system log twice a second !!


 
Oct 10 10:10:10 macOS TeamViewer_Desktop[101]: InterProcessBase::HandleRetryTimer(): Retrying TCP communication (some processes failed to respond: 0 / 5)
Oct 10 10:10:10 macOS TeamViewer_Desktop[101]: InterProcessBase:: StartTcpCommunicationInternal(): setting m_NetworkConnector to new TCP connector
Oct 10 10:10:10 macOS TeamViewer_Desktop[101]: Opening local TCP connection to XXX.XX.XXX.XXX
Oct 10 10:10:10 macOS TeamViewer_Desktop[101]: Local TCP connection failed with error 61
Oct 10 10:10:10 macOS TeamViewer_Desktop[101]: CTcpProcessConnector::CloseConnection(): PID=0
Oct 10 10:10:10 macOS TeamViewer_Desktop[101]: CTcpProcessConnector::CloseConnection(): Shutdown socket returned error 9: Bad file descriptor
 


Can anyone explain this ? I don't see why this would be necessary.


Issue on Reddit: https://www.reddit.com/r/teamviewer/comments/9mxeqn/macos_repeating_console_system_logs_while/

I'm tending to uninstall TeamViewer until this error is solved, since I don't like my system logs to be spammed this much.


Comments

  • mz1
    mz1 Posts: 3

    Also, after uninstalling TeamViewer, the Console still reports the system logs mentioned above.

    So something must be wrong here !

    See Community Thread

  • OZZIE
    OZZIE Posts: 4

    HELLO?? I guess this is why kernal_task is always at at least 30% CPU...

    I quit 'TeamViewer_Desktop' but it seems to start itself again only after a few seconds... I have disabled start on boot but haven't restarted since.

    Please address this issue guys, it's been a while.. ;) 

    I have MacOS Catalina (19A602)

  • OZZIE
    OZZIE Posts: 4

    50% average CPU it uses wonderful...

  • OZZIE
    OZZIE Posts: 4

    I guess since nobody cares about this here's a guide to fully uninstall it https://www.quora.com/How-do-you-completely-uninstall-TeamViewer-on-a-Mac-OSX

    As it still keeps running you have to remove this **bleep** manually also

    get a list of stuff that needs to be stopped:

    sudo launchctl list | grep com.teamviewer
    example for stopping it:

    sudo launchctl remove com.teamviewer.Helper
    sudo launchctl remove com.teamviewer.desktop

    Now kernel_task has dropped for me to an average 15%.. instead of 40-50% 

     

     

  • OZZIE
    OZZIE Posts: 4

    It still keeps running **bleep**.. unless you force quit it.. and then when it has "uninstalled" you now get this **bleep**:

    Nov 19 08:40:36 eton-bor-mac30 com.apple.xpc.launchd[1] (com.teamviewer.desktop[49288]): Service exited with abnormal code: 78
    Nov 19 08:40:36 eton-bor-mac30 com.apple.xpc.launchd[1] (com.teamviewer.desktop): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
    Nov 19 08:40:46 eton-bor-mac30 com.apple.xpc.launchd[1] (com.teamviewer.desktop[49292]): Service could not initialize: Unable to set current working directory. error = 2: No such file or directory, path = /Applications/TeamViewer.app/Contents/Helpers/: 19A602: xpcproxy + 14907 [673][799A5779-E2CE-33EB-81E8-3B5B047C0D40]: 0x2