GLib (gthread-posix.c): Unexpected error from C library during 'pthread_mutex_lock': Invalid argument. Aborting.

[Sergei Vorobyov]

Sorry for disturbing you once again, but what would be the best way to
collect debugging information for vaapisink? This error happens randomly,
sometimes not at all, sometimes after a long run. It seems like a
combination of several random events. So valgrind is not an option.

This comes from my syslog:

Oct 13 15:54:47 nuc3 kernel: [   61.847606] vaapidecode4:sr[1550]: segfault
at 1000110 ip 00007fbcbcdc4414 sp 00007fbc8de9c750 error 4 in
libpthread-2.19.so[7fbcbcdba000+19000]
Oct 13 15:56:52 nuc3 kernel: [  186.838264] traps: vaapidecode4:sr[2376]
general protection ip:7f5d4df24414 sp:7f5d10d79750 error:0 in
libpthread-2.19.so[7f5d4df1a000+19000]
Oct 13 17:08:18 nuc3 kernel: [ 4188.176224] vaapidecode4:sr[2778]: segfault
at b00000077 ip 00007f9963747414 sp 00007f99260d5750 error 4 in
libpthread-2.19.so[7f996373d000+19000]
Oct 13 17:08:43 nuc3 kernel: [ 4213.496231] vaapidecode5:sr[2809]: segfault
at c0500003be2 ip 00007f6721078414 sp 00007f66e40cb750 error 4 in
libpthread-2.19.so[7f672106e000+19000]
Oct 13 17:09:03 nuc3 kernel: [ 4233.580294] vaapidecode5:sr[2840]: segfault
at eee000031c1 ip 00007ff634ddd414 sp 00007ff5f7d96750 error 4 in
libpthread-2.19.so[7ff634dd3000+19000]
Oct 13 17:12:57 nuc3 kernel: [   51.432403] traps: vaapidecode3:sr[2080]
general protection ip:7f934f3cb414 sp:7f9312448750 error:0 in
libpthread-2.19.so[7f934f3c1000+19000]
Oct 13 17:13:22 nuc3 kernel: [   76.441344] vaapidecode4:sr[2182]: segfault
at 4820000000f ip 00007ffc5b962414 sp 00007ffc1e8d6750 error 4 in
libpthread-2.19.so[7ffc5b958000+19000]

Calling

gst_debug_set_threshold_for_name ("vaapi*", GST_LEVEL_LOG);

does not seem to produce any effect.

Thanks!

On Thu, Sep 25, 2014 at 11:20 AM, Sergei Vorobyov <
sergei.vorobyov at facilitylabs.com> wrote:

> After further investigation I narrowed the problem to the following:
>
> 1. I am rendering the video sink on an XWindow, using magic recipes
> described in gstvideooverlay (my intention is to use full screen);
> 2. if I take it away and render in the default window, the problem goes
> away: .wmv files are played OK on i965_drv_video.so with vaapisink
>
> Since my main goal is to use vaapisink, the problem goes away: vaapisink
> implements GstVideoOverlay, and I can directly specify fullscreen,
> rotation, and other properties directly for this sink. #1 is no longer
> needed
>
> On Wed, Sep 24, 2014 at 1:41 PM, Tim Müller <tim at centricular.com> wrote:
>
>> On Wed, 2014-09-24 at 10:01 +0200, Sergei Vorobyov wrote:
>>
>> Hi Sergei,
>>
>> I think what would be most useful for us to help get to the bottom of
>> this is a minimal test program or instructions to reproduce the issue
>> ourselves.
>>
>> Cheers
>>  -Tim
>>
>> --
>> Tim Müller, Centricular Ltd - http://www.centricular.com
>>
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20141013/90e2ea16/attachment.html>