GStreamer 1.18 and a new error. Trying to dispose element pipeline1, but it is in PLAYING instead of the NULL state.

[Nicolas Dufresne]

Le mercredi 23 septembre 2020 à 00:11 +0100, Tim Müller a écrit :
> On Tue, 2020-09-22 at 22:06 +0200, Davide Perini wrote:
> 
> Hi,
> 
> > sometimes when Screen Capturing while gaming I have this error:---(ScreenGrabber:12792): GStreamer-CRITICAL **: 21:55:40.357:Trying to dispose element pipeline1, but it is in PLAYING instead of the NULL state.You need to explicitly set elements to the NULL state beforedropping the final reference, to allow them to clean up.This problem may also be caused by a refcounting bug in theapplication or some element.---
> > Is this something that I can workaround?
> 
> No, it's something you need to debug and fix.
> Could be a problem in GStreamer, but most likely is a
> refcounting/ownership handling issue in your application,or you simply don't set the pipeline to NULL state beforecleaning it up, as the message states.

A plausible hint, if the pipeline was leaked due to a bug in previous GStreamer version, and it's not anymore, this issue could trigger. As said, make sure you set you pipeline to NULL before dropping your ref.
> Cheers Tim
> -- 
> Tim Müller, Centricular Ltd - http://www.centricular.com
> 
> 
> _______________________________________________gstreamer-devel mailing listgstreamer-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/20200923/b03fbeb7/attachment.htm>