Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.
I've just spent over 30 minutes scrolling back through 88 days of a single user chat history. Memory usage has gone from ~300 to ~1000megabytes _on one process_. In total Teams is now using 1.4GB of RAM. And I still have 3 more days to scroll through. Is there an API for chat history? It genuinely might be quicker for me to write my own 'history' app.
Gah! OSX is reporting an increase in memory usage of roughly 5mb per page of messages loaded.
The further you scroll back, the longer it takes for messages to load. It's ridiculous. I know I have to scroll back to the 7th May 2019, because I've searched for the message and I can see *one* message. Now to see the context around that single message, I have to manually scroll back 3 months. If you're not going to fix the scroll lag, then at least show +/- 3 or 4 messages around the search results...
This year-old bug has popped back up, as some of you may have noticed.
It is only affecting users who are scrolled at 85%. If you are experiencing this, please send me user logs so the team can crush this bug!
Thank you :-)