[Bug]: Hardware accelerated videos pulls GPU power in background

Open
#257 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
linux, shell
Domain
desktop

Research direction

The payload names no source files, only the reproduction steps: open a 4K hardware-accelerated YouTube video, switch tabs, and watch GPU decode activity in amdgpu_top. Start by reproducing that on Arch with Wayland, then check whether the repository's Shell launch scripts or flags change hardware video decoding. Done means background tabs stop holding decode activity, or the cause is shown to be upstream Chromium.

Written by the indexing model from the issue text.

Description

bug
Version

Version 0.11.2.1 (Official Build, Chromium 147.0.7727.55) Arch Linux (64-bit) Wayland

Have you tested that this is not an upstream issue or an issue with your configuration?
  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
  • I have tried reproducing this issue in Helium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there
Description

Background video playback keeps draining GPU resources

How to Reproduce?
  1. Open HW accelerated video on Youtube (4K).
  2. Switch to New Tab
  3. Open amdgpu_top
  4. See the Helium DEC(ode) activity in GPU fdinfo procceses.
Actual behavior

Drains GPU power in background

Expected behavior

It should not pull GPU resources in background, like Firefox

Additional context

No response

Dominant language
Shell
Stars
1.1k
Forks
63
Avg merge
28m
Merged PRs (30d)
11

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from imputnet/helium-linux

All issues in imputnet/helium-linux

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.