upgrading to 1.12.4
philippe renon
philippe_renon at yahoo.fr
Wed Jan 24 08:46:47 UTC 2018
I have seen this issue multiple times where enabling "too much" debug log causes pipelines to freeze.
Le Mercredi 24 janvier 2018 9h01, Sebastian Dröge <sebastian at centricular.com> a écrit :
On Tue, 2018-01-23 at 23:02 +0000, David Wells wrote:
> Hi Tim.
>
> We were setting up logging to do the trace and inadvertently turned
> off logging and the chain work.
>
> From that view point we found that if GST_DEBUG=4 or less it works as
> expected. If it is set to 5 or greater the results are what I
> reported.
> It appears the logging is causing the issue.
While that's possible, most likely this just means that your problem is
a race condition somewhere and enabling enough debug output changes
timing enough so that it does not happen anymore.
What would be useful to have would be a stack trace of all threads at
the time when it locks up.
--
Sebastian Dröge, Centricular Ltd · https://www.centricular.com_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20180124/bc1ddf31/attachment.html>
More information about the gstreamer-devel
mailing list