RocketChat / Rocket.Chat

The communications platform that puts data protection first.
https://rocket.chat/
Other
40.84k stars 10.76k forks source link

URGENT .. web client taking more then 1/2 gig of RAM .. need to stop using rocketchat .. #6932

Closed vikaskedia closed 7 years ago

vikaskedia commented 7 years ago

Damm ...

image

image

vikaskedia commented 7 years ago

PLEASE stop adding new features .. and work on this with all focus ..

I love rocketchat and I want it to succeed ..

more than features users need their apps to be snappy ..

I run macbook pro 13 inch without touch bar with 8 GB of memory .. latest chrome stable ..

If it helps you debug .. I can give you VNC access to my laptop .. just let me know ..

neoangin commented 7 years ago

Just use safari on mac for rocket chat and everything will be ok.

vikaskedia commented 7 years ago

In our organization .. Chrome is the only supported browser .. it is deployed to 40 end points using Munki .. and it allows to control various enterprise policies .. like preventing any extension installation .. having preinstalled extensions etc ...

The probability of me being able to move the organization over to Safari from Chrome is less than 1%

geekgonecrazy commented 7 years ago

@vikaskedia I definitely see the cause for frustration. Can you give some details to help us figure out what's causing so much memory usage?

Do you have a lot of channels? How long is your window open before it's using 1gig of Ram? During this time is it sitting here or what kinda actions are you performing? Are there lots of people talking? What kind of content is in your channels? Mainly short conversational messages? Heavy in images or gifs? Large bodies of text?

Please give us as much information as you can to help us reproduce.

engelgabriel commented 7 years ago

@vikaskedia our focus now have not been in adding new features that would make the UI heavier, we have been converting CoffeeScript to JS, adding more unit tests and 2e2 tests, more API options, fixing WebRTC integrations, etc. Our goal now is to make the app more stable and polished so we can launch our version 1.0

The memory issue maybe caused by some caching layer we have been working on, that should make the load time faster, but we will investigate.