Opened 7 years ago

Closed 6 years ago

#11560 closed Bug Report - Crash (Need more Info)

Frontend crashes when changing channel

Reported by: martin@… Owned by:
Priority: minor Milestone: 0.27.1
Component: MythTV - General Version: 0.26-fixes
Severity: high Keywords:
Cc: Ticket locked: no

Description

Since this morning, the frontend has been crashing when trying to change channel.

Since the problem started I've also updated to the latest Mythbuntu packages.

I seem to get two different stack traces, when run in gdb and when run outside gdb. One seems to indicate the NVidia driver, the other libmythavutil. Both will be attached.

MythTV Version : v0.26.0-165-g7150d64 MythTV Branch : fixes/0.26 Network Protocol : 75 Library API : 0.26.20130225-1 QT Version : 4.8.1 Options compiled in:

linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg using_libass using_libxml2

Attachments (2)

back-gdb.txt (20.2 KB) - added by martin@… 7 years ago.
Backtrace running in gdb
back-nogdb.txt (67.2 KB) - added by martin@… 7 years ago.
backtrace running outside gdb

Download all attachments as: .zip

Change History (5)

Changed 7 years ago by martin@…

Attachment: back-gdb.txt added

Backtrace running in gdb

Changed 7 years ago by martin@…

Attachment: back-nogdb.txt added

backtrace running outside gdb

comment:1 Changed 6 years ago by stuartm

Milestone: unknown0.27
Status: newinfoneeded_new

The backtrace in the 'gdb' attachment isn't actually a gdb backtrace which contains a lot more information that the gcc backtrace you see there. It would normally create a backtrace when a segfault is encountered, but it can always be done manually by typing "thread apply all bt full" at the gcc console after mythfrontend has crashed.

Without the gdb backtrace we'd be fishing in the dark, and even with it there's no guarantee.

comment:2 Changed 6 years ago by stuartm

Milestone: 0.270.27.1

comment:3 Changed 6 years ago by sphery

Resolution: Need more Info
Status: infoneeded_newclosed

No "thread apply all bt full" backtrace provided in 7 months.

Note: See TracTickets for help on using tickets.