nextcloud / nextcloud/spreed

Performance issues due to hardware acceleration in Desktop 2.0.3 and Web UI 22.0.x

Open
#16,230 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: frontend 🖌️ high performance 🚀
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • 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.

Is your feature request related to a problem? Please describe.
In linux version 2.0.3 (zip) I'm having a problem that didn't happen before. When I execute Talk Desktop I see random screen glitches until the whole PC hangs and need a hard reset.
This is the same problem that recently started to happen with chromium browser and its derivatives (brave, chrome, etc...)
The way to solve it is turning off hardware acceleration in the browser. In chromium, this can be done from command line and from the menu. But it has to be done from command line because ones executed with hardware acceleration, you can't reach the menu to turn it off because it hangs very quickly.
As you are using a chrome sandbox and because the graphics glitches are the same as with chromium, I believe that that I'm being hit with by problem.

Describe the solution you'd like
I wonder if you can add some way to turn off hardware acceleration. It has to be done in command line or in some configuration file to turn it off before execution.

Describe alternatives you've considered
Turning off hardware acceleration by default and expose the option to turn it on with the appropriate warning.

Additional context
I'm using Ubuntu 24.04.
From what I've found, this problem is happening only on linux.

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

No files, tests, or entry points are named. Start by locating the Desktop 2.0.3 and Web UI 22.0.x launch configuration and the Linux-specific startup path; done would be a supported pre-launch way to disable hardware acceleration, with the affected Linux behavior covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
desktop, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.