High Memory/RAM Usage
Microsoft Teams is currently the most RAM consuming application on my computer
Thank you for your continued feedback. We are continuously improving the clients to use less memory and RAM.
The upgrade to Electron 10 has rolled out fully to the public at this point. Telemetry and testing has shown that this is helping to improve memory performance on the client.
We will continue to work on improvements, and will share more updates as they become available.
For more details on how Teams currently uses memory, please visit https://docs.microsoft.com/en-us/microsoftteams/teams-memory-usage-perf.
Prateek Panwar commented
It hogged 6gb ram once. Restarted back to 600mb. Still 600mb??? what do you expect everyone to have 32gigs? It's too much for this application
running in edge/chrome has disadvantages but improves in this item.
Using a Microsoft Surface Pro. Teams essentially shuts the whole system down several times a day. Have to close everything and restart. Otherwise it takes literally more than 30 seconds to unmute or open chat etc. Unusable
Same here it's literally been messing with my work laptops performance and I'm running windows 10, i5 core, 16GB RAM...
Philip Leitch commented
Congratulations on resetting issue 17219609 that was open for 4 years and was one of the highest voted issues. With no work to resolve the issue the votes have now reset. This strategic fudging of the figures a marvellous strategy.
Solitcon Solitcon commented
1. Uninstall Teams
2. use https://teams.microsoft.com/
Solitcon Solitcon commented
"High memory and RAM usage is something we are continuously working to improve" improve for my laptop or improve for Teams by hogging up more memory?n
My Macbook (Big Sure) is dying when i will start MS Teams. I would like use Zoom, but my company say no. :o(
We are now running the Teams’ New Meeting Experience and with each release of new features the performance of Teams is getting worse:-
• RAM usage - It is growing more resource hungry and now taking up over 1GB or RAM in regular usage.
• Responsiveness – there is a noticeable delay switching from one chat to another or from a chat to a Team
• Black window – switching from Teams to a Meeting there is a 1-2 second black space while Teams struggles to refresh the window.
I have now had multiple IS colleagues report this as a concern and as a reason to not use Teams.
Task Manager shows Teams is consuming 1GB or RAM, while our alternative – Cisco’s Webex app (aka Cisco Spark) is using less than 335MB.
I see 10 MS Teams sub-processes under overall heading of MS Teams. Interesting observation - I tried killing the tasks one at a time (no context what within Teams the subprocess is responsible for). When I killed one of them (still had ~4 subprocesses active), Teams itself died and restarted. When it came back up, one of the subprocesses said "Teams encountered a glitch", was taking 170MB of RAM, but could not find anywhere within the Teams app that said that, just appeared to be a 170MB memory loss.
I went to look at the details, found 10 Teams.exe sessions occupying varying amounts of memory. Total memory usage by all the subprocesses ranged from 610MB to 710MB while I was writing this. Teams is up on my desktop, sitting idle.
With no indication what each of the subprocesses or executable sessions do, various responses from moderators "there's overhead associated, do not be alarmed" seems a bit insulting. If I am running multiple sessions of something, that is when I expect to see multiple executable sessions in task manager. Teams just appears to spool out several sessions. An explanation could help in the short term. Long term, a significant reduction in massive memory usage for an idling app is the better answer.
Attached screenshot of details tab and processes tab showing 10 sessions of Team...at idle
Seriously...I'm not even doing anything (no call nothing)
One more note, that article on how Teams uses memory (as much as it wants) - is crazy! Try running Teams on a 30 user RDS host, it is a business class app correct. I understand Electron is easy to dev for and cross platform friendly, but if it’s this bad on resources it makes Microsoft as a whole look, quite frankly - lazy. We are a MSP, and we need to explain all the time that Microsoft simply doesn’t care or it would be fixed (over four years)!
I concur, there was no reason to split this issue - it all boils down to performance and resource usage. It might not crash if it wasn’t trying to use 1.5 GB of RAM.
I guess an issue with 18k votes was getting to be an issue. I use Teams on a 12 Core 32Gb RAM, NVMe storage workstation and IT.IS.STILL.SLOW. Just try searching a chat thread and see what happens.... ludicrous this hasn’t been resolved in 4 years, likely because it would have to be re-written natively vs using Electron. We have to discourage our customers using it, even if they already have a license under 365.
Teams is idle but consuming > 850MB of RAM for me. Why are so many tasks running simultaneously?
Got over 18,000 votes on the previous 3yr old topic saying that Teams uses WAY TOO MUCH RAM.
I guess that became too embarrassing, so they just blocked further comments and pushed it onto other smaller and less "Hey, my boss might notice 18000 votes" level threads.
Just fix the problem Microsoft!!
It is absolutely ludicrous for a platform to use up >700MB of RAM while it is minimized and in the 'background'.
uses more resources than SQL? we need to work as well as use teams.
Help! Teams is using 850MB of RAM just sitting there, no live comms at the moment And I only have 2 teams In my list. Ugh!
high memory usage by client teams
Maxime Massaer commented
This link https://docs.microsoft.com/microsoftteams/teams-memory-usage-perf given by Alex from MS says it is supposed to use the available RAM and free it for other applications when needed. The current reality is that it doesn't do it at all. It is instead using all the RAM and preventing other applications from running correctly.
Nicolas Fortin commented
Teams desktop app booted up and took up to 1.2G, then stabilized at around 650M. I applied all workarounds, including clearing cache, no changes. Comparatively, Google Chrome is at 600M with only one tab open.