Unreasonably high idle CPU usage

[leoluk]

Description:

Idle CPU usage of Rocket Chat in Google Chrome (latest stable release) is unreasonably high:

Not to mention the 0.6G of RAM.

JS profiler snapshot:

Timeline:

Is this a common issue, or affecting our setup in particular? Happy to privately share the profiler output.

~100 users, with 10-20 active at once. No messages arrived while the profiler was running, with zero user interaction. I checked and it's not receiving anything at all from the websocket.

Can be reproduced by simply leaving Rocket Chat idling on any room.

Nothing at all logged in the console.

Server Setup Information:

• Version of Rocket.Chat Server: 0.64.1 (at 54738c0)
• Operating System: Ubuntu 16.04 LTS
• Deployment Method(snap/docker/tar/etc): custom, from Git
• Number of Running Instances: 1

[geekgonecrazy]

This seems to be related to the desktop app. Please open an issue on: https://github.com/RocketChat/Rocket.Chat.Electron/issues or add to existing issue

[leoluk]

Please re-open, it's a browser issue, not Electron.

[janesser]

Any news here?

[geekgonecrazy]

This still an issue? I’m not aware of it being an issue any more

[janesser]

@geekgonecrazy i would say yes, any input that would help investigation?

[geekgonecrazy]

Would be good to know if this is only active servers or if this is even a server completely idle.

Figuring out with latest version if all originally reported is still true.

Also confirming this is indeed still talking about the browser and not desktop app

[tassoevan]

Just adding here that a cause was found and fixed recently in #12677.

[geekgonecrazy]

Awesome! @janesser are you able to test 0.72.0? Would be great to determine if same or if you have something additional

[catdad]

This is still happening today on the web app.

The rockerchat web app regularly freezes and I need to wait a minute or two before it reacts again. This happens when I try to switch rooms or to type a message after switching a room, and it happens consistently. My coworkers are seeing the same in both the browser application and the Electron application.

[damian-centrone]

This bug in no longer reproducible.