upgrading to 1.12.4

[David Wells]

Hello Sebastian,

I definitely want to provide any data to support fix any gstreamer bugs. Forgive my inexperience in this manor, but when you are asking for the stack trace are you referring to setting GST_DEBUG=7? And that I give you the generated log file? Or, is there a way to get a copy of the trace stack using a windows tool or the like?

Thank you 

-----Original Message-----
From: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] On Behalf Of Sebastian Dröge
Sent: Wednesday, January 24, 2018 2:01 AM
To: Discussion of the development of and with GStreamer <gstreamer-devel at lists.freedesktop.org>
Subject: Re: upgrading to 1.12.4

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