[gstreamer-bugs] [Bug 412678] random segfaults or memory corruptions which seem to be linked to textoverlay

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=412678

  GStreamer | don't know | Ver: 0.10.x




------- Comment #8 from David Schleef  2007-05-13 05:48 UTC -------
This seems to have a lot to do with pango not being reentrant during all its
initialization.

As a really stupid workaround, you might try starting up a pipeline with only
one textoverlay, run a few frames, then shut it down, and then try your
pipeline.  (Of course, you can't do this with gst-launch.)  I'm not sure
there's much we can do about pango not being reentrant.

You could also look into using cairotextoverlay.  It doesn't seem to support
the same parameters; please ask for features you need.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=412678.