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 317470 - [GstCheck] gst_check_teardown_element asserts wrong refcount
[GstCheck] gst_check_teardown_element asserts wrong refcount
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other Linux
: Normal normal
: 0.10.4
Assigned To: Thomas Vander Stichele
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-28 21:20 UTC by Alessandro Decina
Modified: 2006-06-29 14:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alessandro Decina 2005-09-28 21:20:59 UTC 
gst_check_teardown_element uses ASSERT_OBJECT_REFCOUNT (element, "element", 1)
before the element is disposed.
If the element has a bus, it is unref'fed during the element disposal. Since the
bus could contain queued messages having the same element as source, the
refcount could be > 1.
Comment 1 Thomas Vander Stichele 2005-09-29 09:39:53 UTC 
we could fix this by flushing the bus ourselves.  do you have a concrete example
I can work with ?
Comment 2 Alessandro Decina 2005-09-29 10:44:25 UTC 
gst-plugins-good/check/elements/level.c doesn't clean up the element since that
would make the test fail. Flushing the bus before cleaning up the element makes
the test succeed.
Comment 3 Andy Wingo 2005-11-14 17:56:00 UTC 
I don't understand this -- how is cleanup_level called in the first place?
Thomas any clue?
Comment 4 Alessandro Decina 2005-11-15 09:06:35 UTC 
cleanup_level should be called at the end of each test case
Comment 5 Jan Schmidt 2006-01-20 12:07:12 UTC 
ping? :)
Comment 6 Wim Taymans 2006-03-24 11:28:42 UTC 
never seen this fail on the buildbots. closing.
Comment 7 Thomas Vander Stichele 2006-03-28 19:24:42 UTC 
It's never seen on the buildbots because the code is not actually activated - which is what is being said in the bug report.  retargeting and assigning to me.