Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider reverting #345595 Due to memory usage issues in qBittorrent 5.0 #351855

Open
Ember-ruby opened this issue Oct 28, 2024 · 5 comments
Open
Labels
0.kind: bug Something is broken

Comments

@Ember-ruby
Copy link

Describe the bug

qbittorrent/qBittorrent#21502

Steps To Reproduce

Steps to reproduce the behavior:

  1. Open qBittorrent 5.0
  2. Monitor it's memory usage

Expected behavior

qBittorrent should not use excess RAM

Screenshots

Screenshot_28_2104271

Additional context

This issue makes the torrent client utterly unusable, as it just takes RAM and doesn't even seed the torrents

Notify maintainers

@Anton-Latukha @kashw2

Metadata

  • system: "x86_64-linux"
  • host os: Linux 6.11.2, NixOS, 24.11 (Vicuna), 24.11pre690827.5633bcff0c61
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.18.8
  • channels(root): "home-manager, nixos"
  • channels(ember): "nixos"
  • nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Add a 👍 reaction to issues you find important.

@Ember-ruby Ember-ruby added the 0.kind: bug Something is broken label Oct 28, 2024
@Frontear
Copy link
Member

Ouch, if maintainers aren't available, I could get a revert PR going in a couple hours

@oxalica
Copy link
Contributor

oxalica commented Oct 31, 2024

Ouch, if maintainers aren't available, I could get a revert PR going in a couple hours

XRef: #352499
The version < 5.0.1 contains a RCE CVE. If we need to revert back to an older version, we need to mark it insecure.

@Ember-ruby
Copy link
Author

rock and a hard place here, huh.

@Frontear
Copy link
Member

Frontear commented Nov 1, 2024

I think its probably better to leave the package as is, between picking a potential vulnerability and a memory leak I'd reckon most would settle for the latter.

If there's been any upstream commits with a potential fix I could get it added here as a patch as a temporary fix before a full release, though that will have to wait for rn, since it hasnt been fixed.

@luzpaz
Copy link
Contributor

luzpaz commented Nov 14, 2024

Upstream issue seems to be fixed in qbittorrent/qBittorrent#21618 which is part a v5.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken
Projects
None yet
Development

No branches or pull requests

4 participants