Bug 291821
Summary: | memory leak w/ gstreamer error/failure | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom London <selinux> |
Component: | pidgin | Assignee: | Warren Togami <wtogami> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | stu |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-01-04 03:19:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tom London
2007-09-15 00:29:45 UTC
As indicated in gstreamer message, I filed this upstream here: http://bugzilla.gnome.org/show_bug.cgi?id=477086 Got the following from upstream gstreamer bugzilla: ------- Comment #1 from Tim-Philipp Müller 2007-09-18 08:55 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. Filed this upstream on pidgin here: https://developer.pidgin.im/ticket/3182 Thanks for updating to 2.2.0-2! Here is response to upstream bz: Change History 09/18/2007 10:40:04 PM changed by QuLogic Since you're still using 2.1.1, dupe of #2663. 09/18/2007 11:03:53 PM changed by datallah * status changed from new to closed. * resolution set to duplicate. I'll monitor today, and close if all goes well. thanks, tom Sorry, but this is not fixed. I can make the VIRT size go up by sending myself messages (by about 20-30MB). Now complains about 'play' instead of 'fakesink'. Here are the 'new' error messages: (06:42:09) GLib-GObject: cannot register existing type `GstMixerTrack' (06:42:09) GLib-GObject: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (06:42:09) GLib-GObject: cannot register existing type `GstMixerTrack' (06:42:09) gstreamer: Internal GStreamer error: state change failed. Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer. (pidgin:6684): GStreamer-CRITICAL **: Trying to dispose element play, 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. (06:42:09) gstreamer: Internal GStreamer error: state change failed. Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer. (pidgin:6684): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed (06:42:09) GLib-GObject: invalid unclassed pointer in cast to `GstObject' (pidgin:6684): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed (06:42:09) GLib-GObject: invalid unclassed pointer in cast to `GstPlayBaseBin' (06:42:09) oscar: Incoming rendezvous message of type 1, user Tom London, status 0 (06:42:09) oscar: Sent message to Tom London. (06:42:14) util: Writing file blist.xml to directory /home/tbl/.purple (06:42:14) util: Writing file /home/tbl/.purple/blist.xml (06:42:15) msn: C: NS 000: PNG (06:42:15) msn: S: NS 000: QNG 42 I can no longer reproduce this with pidgin-2.2.2-1.fc8 and pulseaudio enabled. What I do see, however, is that the VIRT size increases by about 32MB for each 'sound' played. This increase lasts about 10-20 seconds or so; VIRT size reverts to prior value. Close? Closing, because I don't think transient peaks in pidgin memory usage while playing sounds are anything directly related to pidgin. |