After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 477086 - pidgin memory leak with GStreamer error: state change failed.
pidgin memory leak with GStreamer error: state change failed.
Status: RESOLVED DUPLICATE of bug 486051
Product: GStreamer
Classification: Platform
Component: dont know
0.10.14
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 520487 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-15 00:39 UTC by Tom London
Modified: 2008-03-09 21:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Tom London 2007-09-15 00:39:09 UTC 
Get the following when running pidgin on Fedora development system:

(17:23:56) gstreamer: Internal GStreamer error: state change failed.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.

(pidgin:729): GStreamer-CRITICAL **: 
Trying to dispose element fakesink, but it is not in 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 seems to cause pidgin to leak about 32MB.  (I killed one instance of pidgin after it grew to over 600MB).

Running gstreamer-0.10.14-3.fc8 (and pidgin-2.1.1-1.fc8).
Comment 1 Tim-Philipp Müller 2007-09-18 08:55:22 UTC 
The first is fixed in -good CVS (sort of, at least the nonsensical error message).

The criticial warning (and memory leak) are probably pidgin bugs (not cleaning up properly in the error code path), so I'd suggest you take it up with them first.

If it's really a GStreamer leak, a small stand-alone test case or a valgrind leakcheck log with full debugging symbols against GStreamer CVS would be very helpful.
Comment 2 Tim-Philipp Müller 2007-10-12 17:36:53 UTC 
Refcount assert came up again elsewhere, and no activity here, so marking as duplicate.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 486051 ***
Comment 3 Tim-Philipp Müller 2008-03-09 21:44:08 UTC 
*** Bug 520487 has been marked as a duplicate of this bug. ***