Bug #4312
TVHeadend doesn't free subscriptions after upgrading to 4.1-2520~geb3e25fb1
0%
Description
Yesterday I upgraded TVHeadend to 4.1-2520~geb3e25fb1, but I noticed that one of last night's DVR recordings failed (time missed) because the subscriptions created for previous DVR recordings on other channels were not released/freed once the recording was done. I'm not really sure what other information I can provide since this isn't a crash, but I haven't restarted TVHeadend yet, so if you know of something that would be helpful, I can still collect it. Thanks!
Files
History
Updated by Michael Marley over 7 years ago
Updated by This is still happening in 4.1-2521~ga71465588. I also noticed that (despite the fact that the show no longer appears in the Upcoming/Current Recordings tab, as long as the subscription continues to run (basically until TVHeadend gets restarted), the file size for the show that was recording continues to grow.
Updated by Jaroslav Kysela over 7 years ago
Updated by Provide '--trace dvr,service,subscription' traces - https://tvheadend.org/projects/tvheadend/wiki/Traces .
Updated by Michael Marley over 7 years ago
Here is the log output with tracing enabled. I scheduled two show to record on two different channels and let it run until after the scheduled times had ended.
Updated by Michael Marley over 7 years ago
Sorry, but that version is FTBFS for me. Here is the log: https://launchpadlibrarian.net/314917152/buildlog_ubuntu-zesty-amd64.tvheadend_4.1-2526~g5cbaac172~zesty_BUILDING.txt.gz.
Updated by Mark Clarkstone over 7 years ago
Updated by Michael Marley wrote:
Sorry, but that version is FTBFS for me. Here is the log: https://launchpadlibrarian.net/314917152/buildlog_ubuntu-zesty-amd64.tvheadend_4.1-2526~g5cbaac172~zesty_BUILDING.txt.gz.
Looks like it's an issue just for Zesty/17.04. It builds fine for all the others.
Note, the build number will be slightly higher due to additional commits to the branch.
Updated by Michael Marley over 7 years ago
It also fails for exactly the same reason on Yakkety: https://launchpadlibrarian.net/314917209/buildlog_ubuntu-yakkety-amd64.tvheadend_4.1-2526~g5cbaac172~yakkety_BUILDING.txt.gz
I suspect the reason why it fails on Zesty and Yakkety but none on any of the Doozer builds is because Doozer only builds up through Xenial. Yakkety and Zesty have GCC 6, which is stricter about this sort of thing.
Updated by Mark Clarkstone over 7 years ago
Michael Marley wrote:
It also fails for exactly the same reason on Yakkety: https://launchpadlibrarian.net/314917209/buildlog_ubuntu-yakkety-amd64.tvheadend_4.1-2526~g5cbaac172~yakkety_BUILDING.txt.gz
I suspect the reason why it fails on Zesty and Yakkety but none on any of the Doozer builds is because Doozer only builds up through Xenial. Yakkety and Zesty have GCC 6, which is stricter about this sort of thing.
Ah, then it's a good thing you're actually building tvheadend for newer versions or this wouldn't have been spotted!
Updated by Eric Valette over 7 years ago
Updated by Just a few words to say I have been hit by the same problem and that it is still in 2523 and 2526 failed to build also on debian for the same reason.
Updated by Jaroslav Kysela over 7 years ago
Try v4.1-2527-ga4eeb8b or later.. There was a bug in the DVR code which caused that some DVR sessions were not terminated under some circumstances.
Updated by Michael Marley over 7 years ago
It seems to stop recording at the correct time now, thanks!