Linux - VAAPI causes freeze on stop on 13.1
#1
Follow up of thread http://forum.xbmc.org/showthread.php?tid=183192

I still have the problem, with 13.1, on archlinux.

As said in the previous thread, I have a backtrace of this (under archlinux, I reproduce this everytime when I stop a HD movie or exit from XBMC, and use VAAPI).

http://pastebin.com/bSwHU3Af
Reply
#2
please post full xbmc debug log too.
Reply
#3
Here it is: http://pastebin.com/ckL3iRJ4
Reply
#4
the build provided by arch uses an unsupported lib of ffmpeg which most likely is the reason for this issue. try to get a proper build of XBMC or build it your own.
Reply
#5
Yeah, I confirm that. Disabling the external ffmpeg and rebuilding the package solved the issue. I'm opening an archlinux bug then...
Reply
#6
In order to avoid those kind of issues we removed the external ffmpeg option for 13.x but distros like Arch and Debian will never learn. They patched the option back and deliberately build crap.
Reply
#7
I understand your point of view, but I don't think they hate me or other users that much. I reported the issue back there. I have no idea why they put ffmpeg back in.

Anyway, I can always make an aur package if necessary...

Closed as duplicate of this one, I didn't find Smile https://bugs.archlinux.org/task/39926
Reply
#8
After a little bit more testing, I still have hangs. But they are not as systematic. I'll try to reproduce this this weekend.
Reply
#9
Arch definititly focuses on their users media center experience:
Severity Low Smile
Reply
#10
Yeah, well, that seems to be the default severity. I don't want to take sides on this one (yeah, call me a coward Smile )

Anyway, I'm starting to have doubts about wheter my ffmpeg is external or not...

Is there a way to check this on my binaries ?
Reply
#11
I also have the problem with a git checkout...
Reply
#12
We may be able to help if you let us know the details.
Reply
#13
Yeah, sure. But in order not to waste everybody's time (as I did in the first post of this thread), I'd like to know how I can be absolutely sure about the ffmpeg version I am using.
Reply
#14
(2014-07-26, 11:20)marco44 Wrote: Yeah, sure. But in order not to waste everybody's time (as I did in the first post of this thread), I'd like to know how I can be absolutely sure about the ffmpeg version I am using.

I would simply uninstall or temporarily rename your system ffmpeg libs. If XBMC still runs, it uses internal ffmpeg.
Reply
#15
Ok. So XBMC is using internal ffmpeg. These traces are from today's xbmc git head. I can do it with 13.1 if it's better...

Here are the traces:

gdb bt full when hung:
http://pastebin.com/ZCzuca08
xbmc.log when hung:
http://pastebin.com/xAPZ9Gsc

A funny thing: exiting the gdb session unblocks xbmc...

Can I provide anything else ?
Reply

Logout Mark Read Team Forum Stats Members Help
Linux - VAAPI causes freeze on stop on 13.10