| Summary: | Every torrent from a torrent sharing site makes ktorrent use 100% cpu and only respond to kill -9 | ||
|---|---|---|---|
| Product: | [Applications] ktorrent | Reporter: | real name <hbbyuwtyba> |
| Component: | general | Assignee: | Joris Guisson <joris.guisson> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | ulatekh |
| Priority: | NOR | ||
| Version First Reported In: | 24.02.2 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
real name
2024-04-13 08:48:43 UTC
I found another torrent that reproduces this. Recently my ktorrent was upgraded automatically to 24.12.0 (Fedora Core 40) and ktorrent ceased to start up successfully -- the GUI freezes, it uses 100% of a CPU core, and stays stuck there. After a lot of semi-random efforts to explore the issue, I eventually discovered it was due to one specific existing torrent. Even re-adding the torrent from scratch causes the problem; as soon as ktorrent finishes adding it (i.e. verifying the existing torrent), ktorrent's GUI freezes & uses 100% of a CPU core. Previously, this torrent worked fine. I can't attach the torrent because it exceeds the minuscule 4000 kB limit, but it's available publicly at https://gofile.io/d/OEBWLu (linked to from https://redd.it/1b5rxc2, which also has a magnet link). You can verify the download with sha256sum: cbf7188ac19e664239abd9df2fcd0b21053f2e4f4b2d29c0ff64c44f50890e62 Subscene V2.torrent |