[gstreamer-bugs] [Bug 621505] Disable memory poisoning by default for releases

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Mon Jun 14 16:48:42 PDT 2010


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

David Schleef <ds> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

--- Comment #8 from David Schleef <ds at schleef.org> 2010-06-14 23:48:36 UTC ---
The overwriting of GstCaps/GstStructure structures caught several bugs when it
was added.  It probably continues to have minor value by triggering valgrind
warnings or segfaults earlier because of errors in external code, and the cost
should be minor since the structure sizes are small and are likely in cache. 
I'd like this to continue to be on, either via autogen.sh or GST_CVS=yes. 
(Better would be a g_free variant that does poisoning based on an environment
variable, but I digress.)

Copying the caps/structures at every operation seems rather expensive in
comparison.  I'm probably missing something, but this seems to be geared more
toward checking for bugs in core, not bugs in external code.

-- 
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