nextcloud / nextcloud/talk-desktop

High memory usage on Windows

Open
#886 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug medium os: Windows 🪟 performance 🚀
Dominant language
JavaScript
Stars
525
Forks
85
Avg merge
8h 5m
Merged PRs (30d)
35

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. Install Windows client.
  2. Open it and leave it.
  3. Check task manager for memory usage.
Expected behaviour

Memory usage shouldn't be this high when compared to Brave that has 10 tabs open and Thunderbird. Ideally, when no calls happening, it should be kept closer to 500mb. It's not an exact number, just a recommendation based on other Electron apps I've seen.

Image

Actual behaviour

Having client open, without any calls, memory usage is over 1000MB.

Desktop client

Talk Desktop client version: 1.0.0-rc.1

Operating system: Windows

Operating system version: Windows_NT 10.0.22631 (Windows 11 Home)

Microphone available: yes

Camera available: yes

Server

This client connects to c.nc.c server.

Notes

I know it's difficult to manage memory usage in Electron apps. So one consideration can be to introduce hibernation mode and setting, like many Electron apps do. User sets a specific time of inactivity, let's say 15 min, and if Talk isn't used in 15 min it hibernates to reduce memory usage. User needs to click a button to reload it (ex: Rambox).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the report with the Windows client version 1.0.0-rc.1, leaving it open without calls and monitoring memory in Task Manager. Investigate the Electron desktop client’s idle memory usage and compare it with the reported Windows 11 environment. Done means the high idle usage is explained and reduced, or the scope and next steps are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, javascript
Domain
desktop, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.