Opened 8 years ago

Closed 8 years ago

Last modified 6 years ago

#10095 closed Bug Report - Crash (Unverified)

mythfrontend crashes with segfault when exiting playback on VNC

Reported by: furti@… Owned by: stuartm
Priority: minor Milestone: 0.25
Component: MythTV - User Interface Library Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

When I run myhtfrontend in a window via VNC (mythfrontend -w -geometry 600x480

  • just to do cutlist editing) it crashes with segfault, when exiting the playback

# mythfrontend --version Please attach all output as a file in bug reports. MythTV Version : v0.25pre-3502-g56336a5 MythTV Branch : master Network Protocol : 69 Library API : 0.25.20111009-1 QT Version : 4.7.2 Options compiled in:

linux debug use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_php using_dvb using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_x11 using_xv using_bindings_perl using_bindings_php using_mythtranscode using_opengl using_vdpau using_ffmpeg_threads using_live using_mheg

ii libqt4-dev 4:4.7.2-0ubuntu6.3

Please find gdb "thr a a bt" attached.

Attachments (1)

mythfrontend_thr_a_a_bt.txt (36.9 KB) - added by furti@… 8 years ago.

Download all attachments as: .zip

Change History (4)

Changed 8 years ago by furti@…

Attachment: mythfrontend_thr_a_a_bt.txt added

comment:1 Changed 8 years ago by stuartm

Milestone: unknown0.25
Owner: set to stuartm
Status: newaccepted

comment:2 Changed 8 years ago by stuartm

Component: MythTV - GeneralMythTV - User Interface Library

comment:3 Changed 8 years ago by stuartm

Resolution: Unverified
Status: acceptedclosed

This backtrace is just as baffling as it was the first time I looked at it, I cannot see why it's crashing here. We're checking that the list isn't empty, so it's not that. There's a mutex lock around all accesses to the list, so it's not a race. There's the slim chance that the pointer is bad but we're not dereferencing it at the line indicated in the BT so that doesn't seem to be the cause either. Add to that we've had no other reports of a segfault here.

I'd say that either the backtrace is just bad for some reason or this a weird VNC interaction that's beyond my understanding and my ability to fix.

Note: See TracTickets for help on using tickets.