Opened 10 years ago

Closed 10 years ago

#7139 closed defect (invalid)

Mythfrontend segmentation fault when exiting Live TV unless already watched a recording

Reported by: stephengrobertson@… Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: MythTV - General Version: unknown
Severity: medium Keywords:
Cc: Ticket locked: no

Description

If I exit from live TV without have watched a recording I get a segmentation fault.

Steps to reproduce: Start Mythfrontend Choose Watch TV from top level menu Press Esc Confirm Exit Live TV

If instead I do the following there is no segmentation fault: Start Mythfrontend Choose Media Library Choose Watch Recordings Play a recording Exit the recording(Doesn't seem to matter about saving/deleting etc) Go up one menu level Choose Watch TV Press Esc Confirm exit

It doesn't seem to matter if the watched recording is in progress or not. I am not trying Live TV while another recording is in progress.

gdb and mythfrontend logs attached.

MythTV Version : 22017 MythTV Branch : trunk Network Protocol : 48 Library API : 0.22.20090919-1 QT Version : 4.5.0 Options compiled in:

linux debug using_oss using_alsa using_backend using_dvb

using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtwebkit using_v4l using_x11 using_xrandr using_bindings_perl using_bindings_python using_opengl using_vdpau using_ffmpeg_threads using_live using_mheg

Attachments (3)

gdb.txt (34.8 KB) - added by anonymous 10 years ago.
configureoutput.txt (2.0 KB) - added by anonymous 10 years ago.
myth.log (21.4 KB) - added by anonymous 10 years ago.

Download all attachments as: .zip

Change History (5)

Changed 10 years ago by anonymous

Attachment: gdb.txt added

Changed 10 years ago by anonymous

Attachment: configureoutput.txt added

Changed 10 years ago by anonymous

Attachment: myth.log added

comment:1 Changed 10 years ago by robertm

Status: newinfoneeded_new

Stephen,

Can you re-test with current .23-fixes and let us know if this is still a problem?

comment:2 Changed 10 years ago by robertm

Resolution: invalid
Status: infoneeded_newclosed

No response, please reopen with a .23 backtrace if this persists under .23.

Note: See TracTickets for help on using tickets.