[mythtv-users] Frontend crash after editing cut points.

Michael T. Dean mtdean at thirdcontact.com
Mon Feb 20 23:13:15 UTC 2012

On 02/18/2012 08:38 PM, John Drescher wrote:
> john at jmd0 /auto/portage/local/layman/jmd-gentoo/app-emulation/wine $
> mythfrontend --version
> Please attach all output as a file in bug reports.
> MythTV Version   : v0.24.2-14-g9743d9c-dirty
> MythTV Branch    : branch-fixes/0.24
> Network Protocol : 63
> Library API      : 0.24.20110505-1
> QT Version       : 4.8.0
> Options compiled in:
>   linux debug using_alsa using_oss using_backend using_bindings_perl
> using_bindings_python using_dvb using_frontend using_hdpvr using_ivtv
> using_mheg using_opengl_video using_opengl_vsync using_qtdbus
> using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc
> using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python
> using_mythtranscode using_opengl using_vdpau using_ffmpeg_threads
> using_mheg
> I get the following crash most times I exit from editing cutpoints in mythtv.
> 2012-02-18 20:34:39.463 TV: OSDDialogEvent: result 1 text Cut to End
> 2012-02-18 20:34:40.920 TV: OSDDialogEvent: result 0 text Save Cut
> List and Exit action DIALOG_CUTPOINT_SAVEEXIT_0
> 2012-02-18 20:34:41.289 Marking recording as watched using offset 8 minutes
> 2012-02-18 20:34:41.289 TV: Attempting to change from
> WatchingPreRecorded to None
> 2012-02-18 20:34:41.295 VDPAU Painter: Clearing VDPAU painter cache.
> 2012-02-18 20:34:41.307 MythPainter: 24 images not yet de-allocated.
> 2012-02-18 20:34:41.404 TV: Changing from WatchingPreRecorded to None
> 2012-02-18 20:34:41.404 ScreenSaverX11Private: DPMS Reactivated 1
> ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to
> objects owned by a different thread. Current thread 2683690. Receiver
> '' (of type 'PreviewGenerator') was created in thread 7fd32827d6d0",
> file kernel/qcoreapplication.cpp, line 469

Contrary to popular belief, MythTV doesn't actually log an error message 
before it dies when it dies unexpectedly (doing so is actually 
impossible).  Therefore, the log excerpt above is probably completely 
useless for determining what happened to cause the crash.  The only 
thing log output up until a crash does is show the last thing the 
application did successfully (or, in this case, the last thing it warned 
about) before it crashed.  Sometimes this allows you to guess what might 
have been happening when it crashed, but a much better approach is to 
determine exactly what happened /when/ the application crashed.  This 
involves getting a "debug-enabled" backtrace, as at:



More information about the mythtv-users mailing list