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

[Davide Perini]

Hi all,
GStreamer is super awesome and I love it :)

Said that since 1.18 I am experiencing a new error never seen before.
I'm runnin the same code as before but with GStreamer 1.18 I have a new
error:

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 before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.
---

Is this something that I can workaround?

Any idea?

Thanks
Davide
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Tim Müller]

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 before

dropping the final reference, to allow them to clean up.

This problem may also be caused by a refcounting bug in the

application 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 before

cleaning it up, as the message states.

Cheers

 Tim

-- 

Tim Müller, Centricular Ltd - http://www.centricular.com

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Nicolas Dufresne-5]

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 before

dropping the final reference, to allow them to clean up.

This problem may also be caused by a refcounting bug in the

application 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 before

cleaning 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 list

[hidden email]

https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel