Bug #485

Tvheadend crash on long recording (> 2GB)

Added by Paul Nolan about 2 years ago. Updated 10 months ago.

Status:InvalidStart date:05/02/2011
Priority:NormalDue date:
Assignee:Paul Nolan% Done:

0%

Category:Demultiplex
Target version:2.13
Found in version:unknown Affected Versions:

Description

HTS Tvheadend git-90e3570

Andreas... apologies, but I don't have a crashlog, but it appears that tvheadend crashed when I was away at the weekend, whilst recording the Royal Wedding. The recorded programme was on for five and a half hours. The resulting mkv file is 2008831499 bytes in size. The timestamps are incorrect and the recording runs for just over an hour and a half as far as i can tell. Other scheduled recordings were not attempted leading me to believe that tvheadend terminated whilst recording this file....
sorry , but not much more to go on...

daemon.log - extract from daemon.log file (40.9 KB) Paul Nolan, 05/02/2011 10:25 pm

mkvinfo.txt Magnifier - mkvinfo summary (3.75 KB) Paul Nolan, 05/02/2011 11:06 pm

History

#1 Updated by Andreas Öman about 2 years ago

  • Status changed from New to Need feedback
  • Assignee set to Paul Nolan

There should be some kind of information in the logfile /var/log/daemon.log

A stracktrace should be in there if it crashed.

#2 Updated by Paul Nolan about 2 years ago

okay. found relevant entries in daemon.log (see attached file)

#3 Updated by Paul Nolan about 2 years ago

#4 Updated by Andreas Öman about 2 years ago

  • Category set to Demultiplex
  • Status changed from Need feedback to Accepted
  • Target version set to 2.13

I wonder if this perhaps is caused by wrapping PTS/DTS timestamps.

I'll have to try to simulate that and see if that's a problem.

#5 Updated by Eric Valette about 2 years ago

This bug looks similar to the bug 362 (incorrect recording after 1H30+) except I have only seen it for broadcast with e-ac3 audio stream and yes the timestamp wraps or at least become inconsistent.

#6 Updated by Adam Sutton 10 months ago

  • Status changed from Accepted to Invalid
  • Found in version set to unknown

Going to close this due to age, if its still happening please re-submit.

Also available in: Atom PDF