When using the pvr.nextpvr add-on in Kodi, I'm seeing the timeshift seek bar break (disappear) in Kodi Leia and Matrix RC1 on two different Android 32-bit devices, but not on Windows 10 64-bit. The two Android devices I'm testing are a phone running LineageOS 17.1, and a Fire TV Stick 4K. It happens after an *exact* amount of buffer time has elapsed (35 minutes and 47 seconds), reproducible every time, even though my buffer minutes on the NextPVR server is set for much more time than this (180 minutes). I've reproduced it using TV channels with HD and SD resolutions, so it doesn't seem specific to the buffer file size, just the length. I'm testing it without having guide data -- I don't know if having guide data changes things, but it's also easier to witness the specific timing of the 35:47 mark being reached if no guide data is present to replace the timeshift buffer length read-out (the denominator).
To be sure, my server's Live TV buffer directory has plenty of storage space, and I checked the system memory usage in Kodi System info and didn't notice any memory leak or anything. Also, neither of the tested Android devices' storage is full. Anyway, it would seem improbable that two different client devices' storage circumstances would result in a bug that occurs at exactly the same amount of elapsed buffer time.
Here's an example log (not verbose), but I don't know if it's really that helpful: https://www.dropbox.com/s/kf5oghi94z7ucp...8.zip?dl=0
In this log, I started watching WKRN at 23:02:04.629, paused playback, and waited. Immediately on reaching 35 minutes and 47 seconds of timeshift buffer, the seek bar disappears, leaving what looks sort of like the realtime controls, but with pause functionality still working, but no seeking ability. In other words, the TV stream at this point can continue to be played and can be paused, with the buffer stream continuing to be captured on the server, but it becomes no longer possible to skip forward or backwards.
Doing math on the log times, I just don't see an obvious error entry, as I would expect it to occur in the log immediately following 23:37:50, but nothing eventful seems to occur there. I can work on producing another log in verbose mode if necessary, but hopefully someone can reproduce this issue on another system and it isn't some weird quirk pertaining to just my server and two Android devices.
To be sure, my server's Live TV buffer directory has plenty of storage space, and I checked the system memory usage in Kodi System info and didn't notice any memory leak or anything. Also, neither of the tested Android devices' storage is full. Anyway, it would seem improbable that two different client devices' storage circumstances would result in a bug that occurs at exactly the same amount of elapsed buffer time.
Here's an example log (not verbose), but I don't know if it's really that helpful: https://www.dropbox.com/s/kf5oghi94z7ucp...8.zip?dl=0
In this log, I started watching WKRN at 23:02:04.629, paused playback, and waited. Immediately on reaching 35 minutes and 47 seconds of timeshift buffer, the seek bar disappears, leaving what looks sort of like the realtime controls, but with pause functionality still working, but no seeking ability. In other words, the TV stream at this point can continue to be played and can be paused, with the buffer stream continuing to be captured on the server, but it becomes no longer possible to skip forward or backwards.
Doing math on the log times, I just don't see an obvious error entry, as I would expect it to occur in the log immediately following 23:37:50, but nothing eventful seems to occur there. I can work on producing another log in verbose mode if necessary, but hopefully someone can reproduce this issue on another system and it isn't some weird quirk pertaining to just my server and two Android devices.
![[Image: H4bSHyM.png]](https://i.imgur.com/H4bSHyM.png)
![[Image: aN9qglJ.png]](https://i.imgur.com/aN9qglJ.png)