<div dir="ltr"><div><div><div><div><div><div>Dear Tim,<br></div>thank you for your suggestion of using <br><span class="gmail-il">GST_DEBUG</span>=*:<span class="gmail-il">6</span> gst-inspect-0.10<br></div>It turns out that enabling debug in this way make the gst-inspect-0.10 program work as we expect and return almost immediately. (compared with running gst-inspect-0.10 without it ).<br><br></div>I am not sure why this is happening. As we are running in an Openstack (QEMU) environment it could be that the plugins are accessing an interface that has a bug (i.e. we do not have audio hardware on the server but there are plugins for audio). <br></div><div>Maybe debug mode does not delay on unresponsive interfaces? <br></div><div><br></div>It turns out that passing this environment variable to our commercial program works too, i.e.<br><span class="gmail-il">GST_DEBUG</span>=*:<span class="gmail-il">6 vglrun CommercialPRogram <br></span></div><span class="gmail-il">no longer delays on the first time we run<br><br></span></div><span class="gmail-il">regards<br></span><div><div><div><div><div><div><div><div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><span style="font-family:arial narrow,sans-serif"><span style="font-size:12.8px"><b>---<br>Simon Michnowicz </b> </span><br>Senior Application Specialist, <span style="font-size:13px;border-collapse:collapse">High-Performance Computing</span></span></div><div dir="ltr"><span style="font-family:arial narrow,sans-serif"><br></span></div><span style="font-family:arial narrow,sans-serif"><span style="font-size:13px;border-collapse:collapse"><div dir="ltr"><b>Research Support Services - eSolutions</b></div><div dir="ltr"><b>Monash eResearch Centre</b></div><div dir="ltr">Monash University</div><div dir="ltr">15 Innovation Walk, Building 75, Clayton Campus</div><div dir="ltr">Wellington Road, VIC 3800</div><div dir="ltr">Australia</div></span></span><div dir="ltr"><span style="font-family:arial narrow,sans-serif"><br></span></div><div dir="ltr"><span style="font-family:arial narrow,sans-serif">T: <span>+61 3 9902 0794</span> <br></span></div><div dir="ltr"><span style="font-family:arial narrow,sans-serif">M: <span>+61 3 0418 302 046</span></span></div><div dir="ltr"><span style="font-family:arial narrow,sans-serif">E: <a href="mailto:simon.michnowicz@monash.edu" target="_blank">simon.michnowicz@monash.edu</a></span></div><div dir="ltr"><span style="font-family:arial narrow,sans-serif"><a href="http://monash.edu/" target="_blank">monash.edu</a></span></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On 2 May 2017 at 17:55, Jan Alexander Steffens <span dir="ltr"><<a href="mailto:jan.steffens@gmail.com" target="_blank">jan.steffens@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><span class="gmail-"><div dir="ltr">On Tue, May 2, 2017 at 9:44 AM Simon Michnowicz <<a href="mailto:simon.michnowicz@monash.edu" target="_blank">simon.michnowicz@monash.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Dear Gstreamer List,<br></div><br>I am trying to debug a commercial application that uses Gstreamer. We are running on a Centos 7 cluster with a variety of graphics cards (i.e. K80) in an Openstack virtual environment.<br><br> When the program runs for the first time on a machine, a considerable time delay occurs (40+ minutes) before the program initializes, although subsequent runs start immediately.<br><br></div>I have traced this delay to a file, ~/.gstreamer-0.10/registry.<wbr>x86_64.bin<br></div>If you delete the file, we can trigger the very long delay when running the program.<br><br></div>I am not a Gsteamer developer, so would be very grateful if anybody could advise me on how this file is created. We are very interested into why it is taking so long to create. This could be a programming issue with the commercial application, but it could also point to some very strange interactions between Gstreamer and the virtual environment.<br></div></div></blockquote><div><br></div></span><div>When GStreamer initializes, it loads metadata from all plugins. Internally, it forks a gst-plugin-scanner process to actually
load the plugins (this shields the application process from crashes
caused by bad plugins and/or libraries). The result of this is cached in the registry file.</div><div><br></div><div>I would attempt to use fatrace (which observes filesystem accesses, system-wide) to watch the plugin scanner load plugins, in order to discover which plugin is causing a delay here.<br></div><span class="gmail-"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div>Are there any tools that we could use to generate this file to confirm that this is in fact the problem?<br></div></div></blockquote><div><br></div></span><div>If the file is missing, just running gst-inspect-1.0 should be enough to regenerate it. <br></div></div></div>
</blockquote></div><br></div></div></div></div></div></div></div></div></div></div>