starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

No Live TV Clients Active but Jellyfin still Receiving and Transcoding Channel #7039

New Issue
Closed
opened 2026-02-07 04:26:20 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-07 04:26:20 +03:00
Owner
Copy Link

Originally created by @jwhaugustine on GitHub (May 27, 2025).

Description of the bug

After a short amount of time with clients viewing TV sources, I'll find the next morning that, with all clients disconnected for several hours, Jellyfin is still receiving and processing TV sources as if a client were watching.

There is actually another bug that very closely matches this, which was marked as resolved.

https://github.com/jellyfin/jellyfin-androidtv/issues/416

After one night of around 8 hours of no clients with just the one TV source transcoding, I'm left with 32 GB of ts file in /var/lib/jellyfin/transcodes.

Reproduction steps

Sign in with a client, known to affect Roku/Android/Firestick.
Watch M3U8 live stream channel. Maybe change the channel a few times.
Return to system dashboard.
Observe on server that a transcode job is still running, consuming compute, storage, and network resources.

What is the current bug behavior?

Server continues processing TV sources even though there are no clients viewing the source, or even connected to the server.

What is the expected correct behavior?

Expected behavior: when no clients are watching a TV stream, Jellyfin is not receiving, transcoding, or processing the source in any way.

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

10.10.7

Specify the build version

10.10.7

Environment

- OS: Ubuntu 24.04.2
- Linux Kernel: 6.8.0-60-generic
- Virtualization: None
- Clients: Web, jellyfin-media-player (Windows, Linux), FireTV, Roku
- Browser: Firefox
- FFmpeg Version: 7.1.1-3-noble
- Playback Method: Direct (though still transcoding...)
- Hardware Acceleration: None on server
- GPU Model: RX 6400
- Plugins: Default
- Reverse Proxy: None
- Base URL: No I don't think I'll publish this to the public.
- Networking: 10Gb LAN, 1GB WAN
- Storage: ZFS multipool

Jellyfin logs

We can discuss this.  I'm not comfortable pasting a giant log while unaware of what specific information it contains that may be private.

Available upon request in discussion.

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

In the bug I linked, its listed as affecting the Android client. However, I would argue that the server itself should be capable of making the determination that it has no clients connected to a stream and therefore has no need to continue processing or performing tasks on it.

Originally created by @jwhaugustine on GitHub (May 27, 2025). ### Description of the bug After a short amount of time with clients viewing TV sources, I'll find the next morning that, with all clients disconnected for several hours, Jellyfin is still receiving and processing TV sources as if a client were watching. There is actually another bug that very closely matches this, which was marked as resolved. https://github.com/jellyfin/jellyfin-androidtv/issues/416 After one night of around 8 hours of no clients with just the one TV source transcoding, I'm left with 32 GB of ts file in /var/lib/jellyfin/transcodes. ### Reproduction steps Sign in with a client, known to affect Roku/Android/Firestick. Watch M3U8 live stream channel. Maybe change the channel a few times. Return to system dashboard. Observe on server that a transcode job is still running, consuming compute, storage, and network resources. ### What is the current _bug_ behavior? Server continues processing TV sources even though there are no clients viewing the source, or even connected to the server. ### What is the expected _correct_ behavior? Expected behavior: when no clients are watching a TV stream, Jellyfin is not receiving, transcoding, or processing the source in any way. ### Jellyfin Server version 10.10.0+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number 10.10.7 ### Specify the build version 10.10.7 ### Environment ```markdown - OS: Ubuntu 24.04.2 - Linux Kernel: 6.8.0-60-generic - Virtualization: None - Clients: Web, jellyfin-media-player (Windows, Linux), FireTV, Roku - Browser: Firefox - FFmpeg Version: 7.1.1-3-noble - Playback Method: Direct (though still transcoding...) - Hardware Acceleration: None on server - GPU Model: RX 6400 - Plugins: Default - Reverse Proxy: None - Base URL: No I don't think I'll publish this to the public. - Networking: 10Gb LAN, 1GB WAN - Storage: ZFS multipool ``` ### Jellyfin logs ```shell We can discuss this. I'm not comfortable pasting a giant log while unaware of what specific information it contains that may be private. Available upon request in discussion. ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information In the bug I linked, its listed as affecting the Android client. However, I would argue that the server itself should be capable of making the determination that it has no clients connected to a stream and therefore has no need to continue processing or performing tasks on it.
OVERLORD added the bugstalelive-tv labels 2026-02-07 04:26:20 +03:00
OVERLORD commented 2026-02-07 04:26:23 +03:00
Author
Owner
Copy Link

@jellyfin-bot commented on GitHub (Oct 7, 2025):

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

@jellyfin-bot commented on GitHub (Oct 7, 2025): This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs. If you have any questions you can use one of several ways to [contact us](https://jellyfin.org/contact).
OVERLORD commented 2026-02-07 04:26:25 +03:00
Author
Owner
Copy Link

@jellyfin-bot commented on GitHub (Oct 28, 2025):

This issue was closed due to inactivity.

@jellyfin-bot commented on GitHub (Oct 28, 2025): This issue was closed due to inactivity.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label bug live-tv stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#7039
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?