https://bugs.kde.org/show_bug.cgi?id=527177

            Bug ID: 527177
           Summary: Haruna doesn't terminate yt-dlp process after failed
                    m3u streaming attempt
    Classification: Applications
           Product: Haruna
      Version First unspecified
       Reported In:
          Platform: Flatpak
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

DESCRIPTION
When using a large m3u playlist like iptv-org's, there are streaming URLs that
don't work either because they are not streaming or are geo-blocked. When such
a stream is played, a failed attempt is shown. But, the yt-dlp process lives
and keeps using CPU in the background trying to get the stream to work. As you
keep clicking more such failed streams these yt-dlp processes keep accumulating
in the background taking up resources and thermal throttling the CPU.

STEPS TO REPRODUCE
1. Find a non-working stream and double click to play it, it will show error
playing the stream
2. Find a working stream and play it
3. Notice how yt-dlp process from previous non-working stream is still running
in the background while the working stream's yt-dlp process cleanly exits
4. These stale yt-dlp processes from non-working streams accumulate as more
non-working streams are clicked

OBSERVED RESULT
Failed non-working streams leave stale yt-dlp processes in the background
taking up resources despite switching to a working stream.

EXPECTED RESULT
The yt-dlp process stops once it knows a stream is not working and exits
instead of constantly retrying. When playing another working stream, previous
stream's yt-dlp process doesn't run in the background.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.31.0
Qt Version: 6.11.2

ADDITIONAL INFORMATION
I'm using the KDE nightly Flatpak of Haruna

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to