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 104359 - no way to free a GstMediaInfoStream structure
no way to free a GstMediaInfoStream structure
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks: 104836
 
 
Reported: 2003-01-24 19:45 UTC by Jorn Baayen
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Jorn Baayen 2003-01-24 19:45:42 UTC
The media-info api has no apparant way to free a GstMediaInfoStream structure.
Comment 1 Christian Fredrik Kalager Schaller 2003-05-12 13:05:34 UTC
Assigning to thomasvs and setting 0.6.2 milestone.
Comment 2 Ronald Bultje 2003-05-12 14:54:33 UTC
Can't be done in 0.6.x as it'd be API/ABI breakage.

We'll fix this in 0.7.x/HEAD.

Oh, and Thomas requested for only build bugs to be specifically
assigned to him, so unassigning too.
Comment 3 Jorn Baayen 2003-05-12 14:56:05 UTC
Well you know, *adding* this to an API is usually not considered
breaking it... (and it doesnt break the ABI obviously)
Comment 4 Ronald Bultje 2003-05-12 16:51:07 UTC
Hey Jorn, good to see you back. ;).

(die laatste email naar de rhythmbox mailinglist was wel erg grof hoor
:-p)

Sorry for the dutch, you'll get it. ;). The problem is that in the
ideal case, it'd be a GObject, since everything is supposed to be a
GObject. That'd be ABI breakage. Of course, we could add a _destroy()
function for the time being in 0.6.x... Anyone cares if we solve it
like that?
Comment 5 Ronald Bultje 2003-11-03 10:17:55 UTC
Since this is a 0.6.x-only problem, I'm setting target to 0.6.x.
Comment 6 Ronald Bultje 2004-11-06 09:41:34 UTC
So apprently we never did that. Since 0.6.x is no lonegr maintained, I'll mark
it as wontfix.