[Bug 752147] glimagesink and textoverlay aren't friends on OS X

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Fri Jul 10 16:22:13 PDT 2015


https://bugzilla.gnome.org/show_bug.cgi?id=752147

Julien Isorce <julien.isorce at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |julien.isorce at gmail.com

--- Comment #1 from Julien Isorce <julien.isorce at gmail.com> ---
Created attachment 307285
  --> https://bugzilla.gnome.org/attachment.cgi?id=307285&action=edit
WIP pango: init PangoFontMap and PangoContext when going to READY state

videosink on osx may use NSFont to set title on their window:
initWithContentRect:rect styleMask: NSTitledWindowMask

This function will crash when using the custom NSApp loop
in glimagesink and osxvideosink:
[__NSCFType symbolicTraits]: unrecognized selector
[__NSFontTypefaceInfo _postscriptName]

The patch (even incomplete) seems to fix the problem. But I do not really
understand what happens in the end :)
I thought it was because textoverlay inits its pango fontmap and pango context
before initializing the NSApp. So I defer this in textoverlay from init to
NULL_to_READY.

But then in a real cocoa app, even if I create textoverlay before the NSApp,
the pipeline works and does not crash. So that's still not clear.

Note that the patch is incomplete, it is to start discussion and best way to
fix this. If we do this way (READY_to_NULL) we will need to apply same logic
for other pango elements.

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