Issue/Bug -- DTS = INT64_MIN causes stream failure during Timeshift

userxy79 · 2025-10-25T16:00:21+00:00

Hello, I discovered a very long existing and reproducible issue affecting Live-TV Timeshift in Tvheadend. After several hours of uptime with Timeshift act...

DeltaMikeCharlie

Yet again, today's freeze was identical: 26:30:44 and 00:00:11.

Tomorrow's freeze 'should' occur during my waking hours, so I will be able manually test and see if the freeze only occurs with a long duration timeshift or if any duration will trigger the freeze. Freezes 'should' occur during my waking hours for the next week so I can perform multiple short duration tests if required.

userxy79

Allright, sounds like a plan. So Fingers crossed.

Unfortunately, as much as I wouldreally like to, I cannot really support you in testing the shorter timeshift periods because I do not have a second test system with the required TV card, nor the necessary connections on the satellite system, and I need the long timeshift periods on my live system for some clients. But if there is anything else, let me just know. 😉

Meanwhile yesterday, i cleaned up and finally updated my Posts in tvheadend/tvheadend1931 for a better readability.

DeltaMikeCharlie

userxy79 Unfortunately, as much as I wouldreally like to,

That's OK.

I'm going to test a short timeshift tomorrow morning on my existing LibreELEC unit.

Following that, I going to put in a temporary SSD, build a new clean OS and then test again. After that, I'm going to build with your PR and see what happens.

If short timeshifts also have the problem, then the testing cycle may be shortened because I should be able to target wraparound events.

DeltaMikeCharlie

This morning's test did not freeze. I had been timeshifting for about 2 hours when the wraparound was due but no freeze occurred. This could mean:

TVH is not vulnerable to DTS wraparound error for short timeshifting durations. (How short is short?)
The broadcaster had already wrapped/restarted the DTS for unrelated reasons.
My predicted time was incorrect.

I'm going to let my system continue to timeshift for another 26 hours and see when/if a freeze occurs. If it is still in line with my prediction, I will try a short timeshift the day after.

UPDATE: My system got an INT64_MIN error about 6h30m after the expected time. This suggests to me that the broadcaster may have wrapped/restarted their DTS. This made my total timeshift duration around 08:30:00.

I will test a 2h timeshift at my new projected time tomorrow.

DeltaMikeCharlie

I tested a 2h timeshift a few days ago and no freeze occurred. I have encountered difficulties rebuilding the test system that I was planning to use, so further testing is delayed until those issues are resolved.

userxy79

Thank you for reporting back 😉

Don't worry, it takes as long as it takes and i'm as i said very sorry that i can't test it with you too, related on this specific 2 Hours Test Scenario. Keep me up to date.

userxy79

@DeltaMikeCharlie

So, whats the status on your side? Please give me a little Feedback 😉

DeltaMikeCharlie

userxy79 So, whats the status on your side? Please give me a little Feedback

I have not forgotten this one. 🙂

I am still struggling with my test system configuration. I have my production system that I was able to reproduce the issue with. I also have a test system that I want to run in parallel to test the proposed fix. If the production system has the error and the test system does not, then we have a successful fix.

I need to preserve the current test system because it has work-in-progress that I value. I have tried to install a new SSD/HD, but the machine won't recognise them. My next step will be to use Clonezilla to backup the SSD, I will then install a fresh test system, run the test and then restore the original contents of the SSD.

To add to that, as the test system currently stands, it will not timeshift in the way the the production system does. No matter what I do. I'm sure that it is just a silly configuration parameter that I have missed somewhere, I just need to find it.

Both systems are based on LibreELEC and I would like to keep them roughly aligned, so I have build a LE system with both fixed and standard versions of their TVH addon.

I also work on other projects.

userxy79

Thank you for your quick response. 😉

As for your attempt to add a HDD/SSD that isnt reconized, first try if the disk get reconized in another system. if thats the Case the disk itself is okay. Then check the Cables in the System you failed to add the Disk, plug Cables out and back in, if its not working either, change to the cable where the Disk worked before. If that also fails, try another Port, if that also fails, the system itself where you want to add the Disk is having a Problem. Could be the Port, that is disabled in Bios or damaged or the OS itself is having Issues. Just some Tips to figure out whats the Case for the Problem.

As former Network/systemadministrator i know about the usecase of Production and Test Systems and the limited Resources of Time when working on more then one Project. Beside the Fact that only a handfull of Persons on TVH Project here are available to Help users and fix their Problems.

Even though the faulty DTS handling in TVH after 27.5 hours has already been confirmed several times, tell me what exatcly you wanted to prove with your Testsystem and maybe myself or someone else is able to help out testing.

DeltaMikeCharlie

@userxy79 - Thanks for your advice. I have swapped ports, etc, and the error always followed the drive. At first I thought that the drive was faulty, but then I got similar results with a second drive too.

userxy79 tell me what exatcly you wanted to prove with your Testsystem and maybe myself or someone else is able to help out testing.

I was simply going to run 1 patched and 1 not patched system side-by-side and observe the results. 2 systems with errors will mean that the fix did not work.

I think that my next step with the test system will be to make note of the exact BIOS error messages and then consult the manual.

userxy79

Allright, it was just an Idea from my side to Troubleshoot.

I know real Man`s dont look into Manuals and figure everything out them self,
but hey, sometimes a manual is useful for more than just the tilting chair 😃

As for your comparing patched and unpatched system side-by-side test, that is something i sadly can help you out.

But first things first, and i think in one way or another after consulting your Manual for BIOS Error Messages, it will tell you whats the Problem and what to do to get this fixed 😉

If you need further help contact me and we get this fixed.

« Previous Page