Opened 12 years ago

Closed 11 years ago

#5261 closed defect (fixed)

LiveTV freezes after show ends

Reported by: dscoular@… Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: mythtv Version: 0.21-fixes
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Hi All,

After living with issue http://svn.mythtv.org/trac/ticket/2563 for over a year... I finally took the plunge and upgraded to 0.21 in the hope that I wouldn't have this issue any more.

The issue being that when watching live TV... when the schedule changes over to the next show (on the same channel) the picture freezes and MythTV stops responding to all input except, possibly, the "back" button. This is under mythbuntu 8.04.

Please let me know if you want any more info... backtraces, etc.

Any thoughts ?

Cheers,

Doug

Attachments (2)

mythbackend.log.bz2 (43.4 KB) - added by dscoular@… 12 years ago.
mythbackend -v record log during program transition and frontend freeze.
mythbackend-version.txt.bz2 (393 bytes) - added by dscoular@… 12 years ago.
mythbackend version output

Download all attachments as: .zip

Change History (11)

comment:1 Changed 12 years ago by Shane Shrybman <gnome42@…>

Hi Doug,

Yeah, logs please :)

frontend with -v playback, backend with -v record

From the period covering the transition to the next show.

Might as well throw in the output from mythbackend --version as well.

Changed 12 years ago by dscoular@…

Attachment: mythbackend.log.bz2 added

mythbackend -v record log during program transition and frontend freeze.

Changed 12 years ago by dscoular@…

Attachment: mythbackend-version.txt.bz2 added

mythbackend version output

comment:2 Changed 12 years ago by dscoular@…

Hi Shane,
As requested, I've attached the info you wanted here... Unfortunately, the mythfrontend log was over the upload limit of ~300K at 29M (3M bzipped).

So I've placed all the files up on my web server at the following url:

http://spug.servebeer.com/bug/

mythfrontend froze at exactly:

2008-04-29 15:28:00.176 SetAudiotime? set=1209446880.176826, audt=21697178 atc=21697527 tb=67016 sb=63944 eds=4800000 abps=4 sf=1

This was the last line it managed to log. mythfrontend is frozen with the frame still visible on the screen. mythfrontend won't respond to any input... not even the "back" key (which usually worked when this happened under 0.20-fixes). The backend and rest of linux are quite happy though ;)

I was testing it by watching "World Ahoy: Darwin And The Theory Of Evolution" Tue, Apr 29, 03:23 PM to 03:28 PM (5 mins). I suspect you'll need more debugging info... as there doesn't seem much to go on from the logs.

Hope this helps you get towards the bottom of this long standing issue.

Cheers,

Doug

comment:3 in reply to:  2 Changed 12 years ago by Shane Shrybman <gnome42@…>

Replying to dscoular@gmail.com:

I was testing it by watching "World Ahoy: Darwin And The Theory Of Evolution" Tue, Apr 29, 03:23 PM to 03:28 PM (5 mins). I suspect you'll need more debugging info... as there doesn't seem much to go on from the logs.

Yeah, the backend log looked OK but the frontend log is not useful. We'll need to try again. It looks like there was more than the 'playback' verbose options passed to the frontend. This gives too much info :)

Try to capture the same logs again. Use 'mythfrontend -v playback' on the frontend. And capture from a few minutes before the show ends to a minute or so afterwards.

Are all the clocks perfectly in sync between all the frontend and backend systems?

Also, it looks like this is a dvbrecorder not ivtv?

comment:4 Changed 12 years ago by bde@…

Hi All

I have seen the exact same issue for some time now over diffenrent distroes and hardware .

Have knowledge of others with same problem.

If you need more logs pls say so..

Just upgraded to ubuntu 8,04..Same problem.

BD

comment:5 in reply to:  4 Changed 12 years ago by Shane Shrybman <gnome42@…>

Replying to bde@adslhome.dk:

If you need more logs pls say so..

Yes, more logs please. See the earlier posts on this ticket for what info is wanted and what verbose options should be used.

comment:6 Changed 12 years ago by jim.allen@…

Sorry for the mee too but this problem has plagued me in various forms for svn's going on two years now. In 0.20 it hung the frontend and now in 0.21 it does exactly as you describe. Changing MySql? settings harddrive params etc etc all change it's occurrence rate but it still happens and when it does its always on a program change. I don't have logs yet as I'm building a lab system to replicate the problem and debug to track it down. As soon as I have logs I'll post them. I just thought I'd add to this ticket as I just yesterday read a mythtv-users post from Ismo Tanskanen (RE : [mythtv-users] 0.21: Issue with freezing LiveTV ) where he said that the biggest help in minimizing the problem was to turn on "extra audio buffering". Well I have a production system running 0.21 svn 16962 and doing this has just caused it to watch LiveTV for a full 14 hours without freeze. It is still running and I can assure you that by now that system would have froze around 6 times by now. We need to get to the bottom of this one as some people get it others don't and it seems to be a very hardware/usage thing. Like i said as soon as i have the lab system running and repeating it I'll get back to you and you can help me put the debug logging in the appropriate places to track it down.

Jim :-)

comment:7 Changed 12 years ago by anonymous

Dont have time to play with this before the weekend.

But can confirm Jim's and Ismo Tanskanen's statement .

After activating Extra audio buffer i havent seen any freezing ..

Well still very early to give a final stament..But its definately alot better..

comment:8 Changed 12 years ago by Jim.Allen@…

Any progress on this. I now have two different systems (one 0.21-svn16962 and another 0.20) and both have been freeze free for three weeks, since I selected extra audio buffering. Is this fix as simple as this ?

comment:9 Changed 11 years ago by danielk

Resolution: fixed
Status: newclosed

this should be fixed in head

Note: See TracTickets for help on using tickets.