[Bug 604094] registry: do not remove features when removing a cached plugin that no longer is present

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Mon Apr 18 00:51:48 PDT 2011


https://bugzilla.gnome.org/show_bug.cgi?id=604094
  GStreamer | gstreamer (core) | git

--- Comment #8 from Håvard Graff (hgr) <havard.graff at tandberg.com> 2011-04-18 07:51:47 UTC ---
(In reply to comment #7)
> Wouldn't it be better to store the GstPlugin in GstPluginFeature and do the
> removal properly? Could be done with a weak ref to prevent refcounting circles

I would not know. I am only pointing out a logical error in the code. When you
discover that a plugin has been removed, it never makes sense to remove the
features of that plugin, since those features can't have been registered in the
first place. (since the plugin is gone)

It is like discovering that your pregnant dog has ran of, and then go on to
advertise its puppies for sale... :)

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list