Excessive RAM usage

Liffey · 2023-12-28T09:31:57+00:00

There was an error rendering this rich post.

Liffey

Hello there,

TeamViewer.exe, is always using around 900MB of ram, when idle with no connections.

I don't think it's normal (other machines in my family group never use more than 100MB).

I tried to uninstall and reinstall sw from scratch but with no result.

Anyone can be of help?

Many thanks in advance!

Find more posts tagged with

Accepted answers

heikkuri

TeamViewer 15.50.5 is available and it seems to fix the excessive RAM usage. Now usage is about 52 MB and with one active connection 124 MB.

BryanEnsors

We are also seeing this issue since update to version 15.49

All comments

heikkuri

TeamViewer 15.50.5 is available and it seems to fix the excessive RAM usage. Now usage is about 52 MB and with one active connection 124 MB.

Liffey

Thanks a million. Waiting for a fix, I downgraded to a previous version (15.37.3) and the problem disappeared.

BryanEnsors

We downgraded to 15.48.5 and that solved the issue for us. I have a support case open with TeamViewer with screenshots for over a week with no response.

Liffey

https://community.teamviewer.com/English/discussion/comment/151442#Comment_151442

Unfortunately I have no 15.48.5 available :-(

Is it possible to download it somehow from official TV site?

Cheers

chv_ulrich

https://community.teamviewer.com/English/discussion/comment/151714#Comment_151714

Thanks! I was wondering what **bleep** was wrong with TV for using 800 MB and already considered switching to a different service because of this.

In my case, I noticed it on servers that were running TeamViewer Host and the process that displays the *tray icon* was consuming 800 MB in *each* RDP session! So on a "normal" server where 1-2 admin accounts are constantly logged in (but disconnected), 1.6 GB of memory was wasted for nothing.

If no users were logged on, the TV service process only consumed ~25 MB and with an active connection to the console session, this increased to about 125 MB).

BryanEnsors

We are also seeing this issue since update to version 15.49