Project

General

Profile

Bug #1619

Bug #1605: Timeshift not deleting files until you stop playback.

Timeshift indicates buffer full

Added by Mr. Blond almost 12 years ago. Updated almost 12 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
Category:
Timeshift
Target version:
-
Start date:
2013-02-14
Due date:
% Done:

0%

Estimated time:
Found in version:
3.3.465~g79c134f
Affected Versions:

Description

When I pause LiveTV the log indicates buffer full, see
http://paste.ubuntu.com/1651439/
When I unpause LiveTV it the image freezes and XBMC hangs.
I have tried with the buffer in /run/shm, in /tmp and in my home folder, all the same result.
Problem occurs with Build: 3.3.465~g79c134f

With previous Build: 3.3.414~gce67dd9 there was no problem
http://paste.ubuntu.com/1651453/

History

#1

Updated by Ron L almost 12 years ago

Mr. Blond wrote:

When I pause LiveTV the log indicates buffer full, see
http://paste.ubuntu.com/1651439/
When I unpause LiveTV it the image freezes and XBMC hangs.
I have tried with the buffer in /run/shm, in /tmp and in my home folder, all the same result.
Problem occurs with Build: 3.3.465~g79c134f

With previous Build: 3.3.414~gce67dd9 there was no problem
http://paste.ubuntu.com/1651453/

I think this is the same issue as #1605. For now try setting timeshift On Demand to ON and Max Size to Unlimited. As long as you don't leave it on pause long enough to fill up your drive it seems to work.

#2

Updated by Mr. Blond almost 12 years ago

Ron L wrote:

I think this is the same issue as #1605. For now try setting timeshift On Demand to ON and Max Size to Unlimited. As long as >you don't leave it on pause long enough to fill up your drive it seems to work.

I do not agree, the buffer folder is completely empty...

I will try your solution, but the problem you debscribe in your issue does not match the symptoms I see in my setup...

#3

Updated by Adam Sutton almost 12 years ago

What configuration do you have? it appears to think its full immediately. This would imply the configuration is wrong. Although I think I set full in an error condition as well (but not sure it would generate that log message).

Adam

#4

Updated by Ron L almost 12 years ago

Mr. Blond wrote:

Ron L wrote:

I think this is the same issue as #1605. For now try setting timeshift On Demand to ON and Max Size to Unlimited. As long as >you don't leave it on pause long enough to fill up your drive it seems to work.

I do not agree, the buffer folder is completely empty...

I will try your solution, but the problem you debscribe in your issue does not match the symptoms I see in my setup...

Could be something different, but it sounds exactly like what I was getting. Restart tvheadend between timeshift config changes and run xbmc in windowed mode so that you can monitor your buffer dir at the same time. If I set a Size limit TVH writes buffers until it hits that limit, which doesn't take long when using /run/shm. When you stop play those get deleted, when you tune another channel it won't write any more buffers and your buffer dir will be empty. Won't write buffers again until TVH gets a restart.

#5

Updated by Adam Sutton almost 12 years ago

  • Status changed from New to Invalid
  • Parent task set to #1605

Actually having re-read that I'm inclined to agree with Ron. It does sound like exactly the same issue as #1605. And I'm going to close as such.

I will be posting a fix to #1605 in the next few hours (just bundling up other stuff).

Adam

#6

Updated by Mr. Blond almost 12 years ago

Just compiled TVH fromg git, running Build: 3.3.476~g7088c9c now and timeshift is working again!

#7

Updated by Razor 109 almost 12 years ago

Mr. Blond wrote:

Just compiled TVH fromg git, running Build: 3.3.476~g7088c9c now and timeshift is working again!

For me the problem still persists. The first time after the start of tvheadend the buffer wil fill, only after switching channel i get this error: Feb 15 16:35:15 timshift: ts 1 buffer full
I can only make it work it again by restarting tvheadend.

#8

Updated by Razor 109 almost 12 years ago

edit

problem seems to be fixed when enabling unlimited.
Got the limit on 60min and 3000mb. More than 3000mb free on the drive.

#9

Updated by Adam Sutton almost 12 years ago

Stupid, stupid me, I forgot to actually check it before committing, doh!

I've realised there is actually a more fundamental issue relating to size limits. The problem is I'd always assumed the time period would be set to represent a smaller size than the total size etc... This is clearly not the case if setting a reasonable size limit and unlimited time (not unreasonable and entirely expected), and the code doesn't cope with this.

Adam

#10

Updated by Mr. Blond almost 12 years ago

Sorry, I still have the same problem...
Only a restart of TVH results in proper timeshift behaviour and then for only 1 time.

#11

Updated by Adam Sutton almost 12 years ago

try it now.

#12

Updated by Ron L almost 12 years ago

Adam Sutton wrote:

try it now.

Hmmm, I never ever change the time setting. Should I be doing so? Buffer file sizes can vary so much from one channel to the next it's hard to guage where to set it.

I'm getting a lot of crashes. Trying to sort out under what conditions. One consistent one seems to be On Demand set to Off and Unlimted size set to OFF it will crash everytime when I change the channel.

http://pastebin.com/qTP4pZuY

On demand set to On and Unlimited size set off .. . Hit pause.... Hit Play... Change channel... Hit pause and it will crash....

http://pastebin.com/SGswb57s

Those two seem consistent. I've had Demand ON, Unlimited off crash randomly while playing back after being paused, but I can't quite get a handle on duplicating those.

With unlimited size ON all seems well as long as the drive doesn't fill up.

#13

Updated by Ron L almost 12 years ago

Forgot version...

./tvheadend: version 3.5.2~gc338802

#14

Updated by Adam Sutton almost 12 years ago

Can you submit that as a new issue, as it looks like something different. Also can you:

1. try and grab a gdb stack trace.
2. include details of the settings you're using
3. the output from ./configure when you ran it.

Ta
Adam

Also available in: Atom PDF