Opened 19 years ago

Closed 19 years ago

#4232 closed defect (invalid)

backend segfaults when switching tuners in liveTv

Reported by: robert.macaulay@… Owned by: Isaac Richards
Priority: major Milestone: 0.21
Component: mythtv Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Just recently upgraded to recent SVN via aatrpms.bleeding, mythtv-backend-0.21-172_trunk_r14921.fc6.x86_64.

# mythbackend --version Source code version : Unknown SVN branch : trunk Library API version : 0.21.20071119-1 Network Protocol Version: 36 Options compiled in:

linux release using_oss using_alsa using_arts using_jack

using_backend using_dbox2 using_dvb using_firewire using_frontend using_hdhomerun using_iptv using_ivtv using_joystick_menu using_lirc using_opengl_vsync using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmcw using_xvmc_vld using_bindings_perl using_opengl using_libavc_5_3 using_live

Started getting a segfault when changing tuners in liveTv mode. It's pretty reproducible. System has 2 disks in the default storage group.

Attachments (4)

gdb.txt​ (41.4 KB ) - added by anonymous 19 years ago.
gdb stack trace
myth.log​ (4.1 KB ) - added by anonymous 19 years ago.
myth.log
myth2.log​ (18.5 KB ) - added by anonymous 19 years ago.
Second crash during normal playback
gdb2.txt​ (27.0 KB ) - added by robert.macaulay@… 19 years ago.
Second crash during normal playback

Download all attachments as: .zip

Change History (9)

by anonymous, 19 years ago

Attachment: gdb.txt​ added

gdb stack trace

by anonymous, 19 years ago

Attachment: myth.log​ added

myth.log

comment:1 by robert.macaulay@…, 19 years ago

It crashed again during playback. Same stack traces it seems. Attaching as myth2.log and gdb2.log

by anonymous, 19 years ago

Attachment: myth2.log​ added

Second crash during normal playback

by robert.macaulay@…, 19 years ago

Attachment: gdb2.txt​ added

Second crash during normal playback

comment:2 by stuartm, 19 years ago

Milestone: unknown → 0.21

comment:3 by danielk, 19 years ago

From a quick look at the backtrace this appears to be some problem with the Autoexpirer code.

comment:4 by robert.macaulay@…, 19 years ago

I think it's been fixed. After an update to newest SVN, it stopped happening. This can be closed

comment:5 by cpinkham, 19 years ago

Resolution: → invalid
Status: new → closed

Closing at users request.

Note: See TracTickets for help on using tickets.