Opened 16 years ago

Closed 15 years ago

#8979 closed defect (Fixed)

[CRASH] LiveTV changing channels cause fe crash

Reported by: warpme@… Owned by: cpinkham
Priority: minor Milestone: 0.25
Component: MythTV - Video Playback Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Scenario to reproduce:

1.lauch LiveTV
2.start to change channels

3.after 2-10 changes FE usually crashes

fe (trunk 26423) logs attached

Attachments (3)

mythfrontend-fe-test.log.zip​ (8.9 KB ) - added by warpme@… 16 years ago.
FE log
logs.tar.gz​ (23.6 KB ) - added by warpme@… 16 years ago.
FE/BE logs
myth_debug.tar.gz​ (36.8 KB ) - added by warpme@… 16 years ago.
FE backtrace

Download all attachments as: .zip

Change History (23)

by warpme@…, 16 years ago

Attachment: mythfrontend-fe-test.log.zip​ added

FE log

comment:1 by Nicolas Riendeau, 16 years ago

Status: new → infoneeded_new

warpme, are you still having that problem?

comment:2 by anonymous, 16 years ago

I'm seeing this here too. My current suspicion is that the backend is expiring a bunch of short live tv segments at the same time and this is somehow blocking access to the new live tv recording.

Can you attach the output of both mythfrontend and mythbackend with -v playback,file verbosity

Also, what tuners are you using?

comment:3 by markk, 16 years ago

Status: infoneeded_new → new

Just to clarify the tuner info, I'm also wondering whether this is some sort of lock up with the ivtv (pvr-150 etc) driver.

comment:4 by beirdo, 16 years ago

Status: new → infoneeded_new

comment:5 by warpme@…, 16 years ago

Hi,
Sorry for late replay (I was on business trip)
Pls find FE/BE logs. My sys has 2XDVB-S2 + 1xDVB-T tuners. FE/BE under test was SVN26493.
br

by warpme@…, 16 years ago

Attachment: logs.tar.gz​ added

FE/BE logs

comment:6 by robertm, 16 years ago

Status: infoneeded_new → new

comment:7 by robertm, 16 years ago

Milestone: 0.24 → unknown
Priority: major → minor
Severity: high → medium

warpme, you have been around long enough to know that you are not to set milestones, priorities, or severities on tickets.

comment:8 by robertm, 16 years ago

Status: new → assigned

comment:9 by robertm, 16 years ago

Status: assigned → infoneeded

Does anyone have a backtrace of this crash?

comment:10 by warpme@…, 16 years ago

Unfortunately for me it is not easy to do backtrace of crash, as my FE is running on minimal, remote booted environment. If nobody else will help here - I will try install mythbuntu on VM and try to reproduce crash with backtrace. Unfortunately lack of time not helps here :-( Any hints helpful to minimize time spent on backtrace creation are well appreciated.

comment:11 by robertm, 16 years ago

warpme,

As you are the original reporter, unfortunately the responsibility is on you to be able to produce a backtrace. Please attach at your earliest convenience. See section 22 of the manual and the wiki page on debugging.

comment:12 by warpme@…, 16 years ago

Fortunatelly my friend help me with quick setup gdb-equipped environment. Here are backtraces for frontend. FE was on 26655. br

by warpme@…, 16 years ago

Attachment: myth_debug.tar.gz​ added

FE backtrace

comment:13 by robertm, 16 years ago

Owner: changed from Janne Grunau to markk
Status: infoneeded → assigned

Crashing on MythPlayer::GetEncodingType. Unable to get the decoder?

comment:14 by robertm, 16 years ago

Note that there are two issues here-- the fact that we are calling GetEncodingType on a null recording (which is just the symptom causing the segfault) and an apparent RingBuffer problem where we mercilessly are attempting to read after some sort of communications or socket error and safe_read is failing again and again. This may be a multiple-assignee bug.

comment:15 by markk, 16 years ago

The NULL pointer crash was fixed in r26685. As robertm has already mentioned, it is probably a symptom of the overall problem rather than the cause.

comment:16 by warpme@…, 16 years ago

Robert, Mark

Thx. No more FE crashes. We can close ticket. Unfortunately Mark is right: FE crash is a symptom more general problem with my LiveTV. I'll move to commits mailing-list for details. thx

comment:17 by robertm, 16 years ago

Owner: changed from markk to cpinkham

Chris, reassigning to you for the rest, hoping you can look at the safe_read issue in the FE log and determine if there's a RB bug there.

comment:18 by beirdo, 16 years ago

Summary: LiveTV changing channels cause fe crash → [CRASH] LiveTV changing channels cause fe crash

comment:19 by warpme@…, 15 years ago

Hi, After switching to latest master I didn't observe this issue on 24/7 working production system. From my perspective we can close this ticket with status resolved.

comment:20 by beirdo, 15 years ago

Milestone: unknown → 0.25
Resolution: → Fixed
Status: assigned → closed
Note: See TracTickets for help on using tickets.