[Bug 789473] vaapi plugins removed from registry at early boot

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=789473

--- Comment #13 from Florent Thiéry <florent.thiery at ubicast.eu> ---
On the first boot, creating the display does work:

0:00:01.231246780   311 0x56038bc4f800 INFO            vaapidisplay
gstvaapidisplay.c:899:gst_vaapi_display_create_unlocked:<vaapidisplaydrm0> new
display addr=0x56038c2da0c0

On the second boot, when creating , creating the VA display fails:

0:00:00.074045621   326 0x55d8657a3800 ERROR                default
gstvaapi.c:254:plugin_init: Cannot create a VA display


By catting /proc/uptime, we can see that the script is executed at 2.29s
uptime, and completes at 7.03
Mar 28 12:44:11 mediacoder vaapi.sh[301]: 2.29 5.56
Mar 28 12:44:16 mediacoder vaapi.sh[301]: 7.03 16.79

Identically, the second boot, the scripts completes at 4.93s
Mar 28 12:45:05 mediacoder vaapi.sh[306]: 2.27 5.52
Mar 28 12:45:08 mediacoder vaapi.sh[306]: 4.93 11.41

Funnily, adding a sleep to the script before running gst-inspect does seem to
fix it:

# cat /usr/local/bin/vaapi.sh 
#!/bin/bash
cat /proc/uptime
sleep 5
GST_DEBUG_NO_COLOR=yes GST_DEBUG=7 /usr/bin/gst-inspect-1.0 vaapih264enc &>
/home/ubicast/vaapi.txt
cat /proc/uptime

What seems to happen is some kind of race condition, where the gstreamer cache
is so efficient that the moment where vaapi is probing the display is too soon
and will fail.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.