Opened 8 years ago

Closed 8 years ago

#10105 closed Bug Report - General (Fixed)

mythfrontend crashes when watching any video (LiveTV, recordings, videos)

Reported by: amlopezalonso@… Owned by:
Priority: minor Milestone: 0.25
Component: MythTV - Video Playback Version: Master Head
Severity: high Keywords: mythfrontend, intel,
Cc: Ticket locked: no

Description

After upgrading to Mythbuntu 11.10, watching LiveTV, recordings or videos have became impossible probably due to a clash between intel GPU drivers and QT4. Mythfrontend crashes with a:

mythfrontend.re[6517]: segfault at 1665c ip 00007fbf0c3bcfb4 sp 00007fffa70bb130 error 4 in i965_dri.so[7fbf0c38b000+b4000

When launching a backtrace (gdb mythfrontend.real -x gdbcommands), the app just freezes at "Please Wait" though.

Attaching backtrace

Regards, Antonio

Attachments (2)

gdb.tar.gz (47.6 KB) - added by amlopezalonso@… 8 years ago.
mythfrontend.log (34.1 KB) - added by amlopezalonso@… 8 years ago.

Download all attachments as: .zip

Change History (12)

Changed 8 years ago by amlopezalonso@…

Attachment: gdb.tar.gz added

comment:1 Changed 8 years ago by markk

Milestone: unknown0.25
Status: newinfoneeded_new

Can you attach a fresh log from one instance of 'mythfrontend -v playback --loglevel=debug'

(i.e. start mythfrontend with a fresh log, navigate to watch recordings and play a recording)

and please make sure mythwelcome isn't running/used.

Thanks

Changed 8 years ago by amlopezalonso@…

Attachment: mythfrontend.log added

comment:2 Changed 8 years ago by amlopezalonso@…

Attaching log

Regards, Antonio

comment:3 Changed 8 years ago by danielk

This may be a dup of #10100. Can't be sure without backtrace.

comment:4 Changed 8 years ago by amlopezalonso@…

mmmmm I already attached one. Isn't it valid?

comment:5 Changed 8 years ago by danielk

Sorry, I missed that. It looks like this isn't a dup of #10100.

comment:6 Changed 8 years ago by amlopezalonso@…

I grabbed a nvidia card so I could keep MythTV on the run. Effectively closing #10100 didn't solve the problem.

comment:7 Changed 8 years ago by linux@…

I am seeing the same issue on Ubuntu 11.10 on a notebook with the Intel i915 driver:

Program received signal SIGSEGV, Segmentation fault.
intelDRI2Flush (drawable=0x8891908) at intel_screen.c:111
111	intel_screen.c: No such file or directory.
	in intel_screen.c
(gdb) bt
#0  intelDRI2Flush (drawable=0x8891908) at intel_screen.c:111
#1  0x04f45c99 in dri2SwapBuffers (pdraw=0x8891860, target_msc=0, divisor=0, 
    remainder=0) at dri2_glx.c:547
#2  0x04f1d21c in glXSwapBuffers (dpy=0x835e850, drawable=62914578)
    at glxcmds.c:738
#3  0x04eb5884 in QGLContext::swapBuffers() const ()
   from /usr/lib/i386-linux-gnu/libQtOpenGL.so.4
#4  0x00673102 in VideoOutputOpenGL::Show (this=0xac415b78, 
    scan=kScan_Interlaced) at videoout_opengl.cpp:584
#5  0x0058531c in MythPlayer::AVSync (this=0x8fc0d80, buffer=0xac438028, 
    limit_delay=true) at mythplayer.cpp:1854
#6  0x0059f632 in MythDVDPlayer::AVSync (this=0x8fc0d80, frame=0xac438028, 
    limit_delay=false) at mythdvdplayer.cpp:382
#7  0x00588779 in MythPlayer::DisplayNormalFrame (this=0x8fc0d80, 
    check_prebuffer=true) at mythplayer.cpp:2163
#8  0x00589328 in MythPlayer::VideoLoop (this=0x8fc0d80) at mythplayer.cpp:2313
#9  0x0059e738 in MythDVDPlayer::VideoLoop (this=0x8fc0d80)
    at mythdvdplayer.cpp:212
#10 0x00511530 in TV::PlaybackLoop (this=0xa6ae0e08) at tv_play.cpp:1282
#11 0x00500dfd in TV::StartTV (tvrec=0xa989c298, flags=0) at tv_play.cpp:337
#12 0x0808c988 in internal_play_media (mrl=..., plot=..., title=..., 
    subtitle=..., director=..., season=0, episode=0, inetref=..., lenMins=0, 
    year=..., id=...) at main.cpp:1158

I did some googling and it looks like a bug in the current mesa version 7.11: https://bugs.freedesktop.org/show_bug.cgi?id=37177

comment:8 Changed 8 years ago by markk

Owner: markk deleted

comment:9 Changed 8 years ago by linux@…

Hi,

I tried with the current master branch and cannot see the problem anymore. It seems to be due to commit f629fc199e870c6381d889d539c6a8ecd41bfdf4. When I back out this single commit, the crashes appear again. If possible, I would like to see this included in 0.24 ;-)

Best wishes,

Martin.

comment:10 Changed 8 years ago by danielk

Resolution: Fixed
Status: infoneeded_newclosed

This appears fixed in trunk according to linux@….

Note, we're unlikely to backport as 0.25 is entering feature freeze tonight.

Note: See TracTickets for help on using tickets.