Skip to content

Gst.Pipeline never disposes Gst.Bus

Submitted by Justin Kim @joykim

Link to original bug (#794316)

Description

To explain leakages, I created unit tests in my personal repository.

https://github.com/justinjoy/Gst.Tests/blob/master/Gst.Tests/PipelineTests.cs

There are 4 tests;

  • TestPipelineDispose: disposing of pipeline instance only (Test failed)
  • TestPieplineParseAndDispose: same as above, but the pipeline is created by Parser.Launch (Test failed)
  • TestPipelineDisposeManually: Explictly calling 'Dispose' for all exising element (Test passed)
  • TestPieplineUriDecodebinForcedlyDispose: Almost same as above, but disposing of child elements in 'deep-element-removed' callback. (Test passed)

So what I found is that the binding causes leakages as long as a programmer doesn't manage Gst.Element, currently. But, still I am not sure if they should be managed in gstreamer-sharp, or application.

I'll add some patches to make my unit tests pass successfully.