Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible memory leak #710

Closed
3 tasks done
divanikus opened this issue Feb 14, 2018 · 6 comments
Closed
3 tasks done

Possible memory leak #710

divanikus opened this issue Feb 14, 2018 · 6 comments

Comments

@divanikus
Copy link

I confirm (by marking "x" in the [ ] below: [x]):


Summary
Mattermost Desktop consumes constantly increasing amount of memory. I have something around 20 open channels and severl dialogues with other users. Memory consumption after cold restart was around 250 MB, after 5 hours it's around 750 MB. We also saw 1000 MB on one of our collegues desktop.

Steps to reproduce
Just use it for while and look at memory consumption in your Task Manager.

Version numbers

  • MS Windows 10 Pro 1709, MacOS X 10.13
  • Mattermost Desktop App Version 4.0.0
  • Mattermost Server 4.5.0 (4.5.1, postgres) - Omnibus GitLab install v10.4.3

Expected behavior
Memory consumption remains low.

Observed behavior
Growing memory consumption.

@jasonblais
Copy link
Contributor

@divanikus Do you know if the happens on a browser?

I suspect it might be from loading more data over time as you switch channels (and receive new messages).

@divanikus
Copy link
Author

divanikus commented Feb 15, 2018

I can confirm that in-browser version also consumes memory, but at lesser amount. After 3 hours I see 350 MB for a Chrome tab and 1075 MB for desktop app.
84320f00379ba237c0761a13ee52f7d2
d129602a33d82eb1e0ffc0179de62d17

@divanikus
Copy link
Author

Ok, switching between channels boosts memory consumption at both in-browser and desktop app. I got 600 MB in Chrome in 2 minutes by simply switching between channels.

Anyway, it's totally not OK.

@divanikus
Copy link
Author

Ok, I've reported an issue for server too mattermost-server#8297

@yuya-oc
Copy link
Contributor

yuya-oc commented Feb 15, 2018

Thanks. As you saw on Chrome, switching channel increases memory consumption. The process is merely executing the webapp JavaScript as well as Chrome. So the desktop app can't control the consumption.

@jasonblais
Copy link
Contributor

@divanikus I'll close this issue for now, and we can continue discussion at mattermost/mattermost#8297

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants