@Microsoft, Teams dev team - can we consider this to be a memory leak (security issue)? I see my CPU (8th gen i7 w/8 cores) is running about 30% CPU all the time when Teams is just sitting in the background. This just started recently, presumably after
some kind of update or after the message DB grew beyond a certain size? Is it possible to have corruption in the database files?
It really is liking the resources though because I changed process priority to real-time (24) it begins to be more responsive - there are still delays but they are only 1-2 seconds as opposed to the typical 5-10 second delays before text appears that I just
typed, or my mouse cursor stops being frozen, etc.
I hope that you are able to turn things around with this application...it has really taken a downward dive here with the resource problem but I'm sure it's a top priority and being worked on, given the amount of time gone by here though it must be difficult
to fix. I'm looking closely at what's happening in Process Explorer (https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer)
as well. If any details would be helpful for Microsoft resolving this issue, please let me know and I will provide them.