[gstreamer-bugs] [Bug 344900] New: A Blank Package name cause Registry Dump everytime gstreamer runs

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=344900
 GStreamer | gstreamer (core) | Ver: 0.10.6

           Summary: A Blank Package name cause Registry Dump everytime
                    gstreamer runs
           Product: GStreamer
           Version: 0.10.6
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: keith.preston at garmin.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
This problem only comes up with an incorrect definition of a plugin (incorrect
in the sense that it has a blank package name).  However it did show a flaw in
the XML registry  system that should be fixed, although it should be fairly
easy.  The basic problem is that initialization from a pluging will accept a
blank package, however if this is written to the cache and read back out of the
cache, it is not parsed correctly.

Because of a build system problem which has been patch, I ended up with
libcoreelement having a package name of "".   The first time this plugin loads
it will cause a registry cache to dump out.   In the xml it will have a blank
package, i.e. <package></package>.  However the next time that the plugin loads
it will error out when reading this description back in (message is "problem
reading plugin").  I believe that this is a problem in the function
read_string.  It would seem to be returning a 0 when two corresponding tags are
right next to each other.

Steps to reproduce:
1. Quite simply change your XML cache (.gstreamer/registry.*.xml) and change
one of the plugins package name to "" (i.e. <package></package>)
2. 
3. 


Actual results:
If you do this step, everytime gst-launch is invoked it will re-write out the
xml cache in full (slows down start up time)   I could especially see this in
scratchbox sbrshd where NFS writes are slow.   It was causing a 20-30 second
delay

Expected results:


Does this happen every time?
Yes

Other information:


-- 
Configure bugmail: http://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.