[Bug 691484] New: Crash in osxvideosink when displaying on Qt widget

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=691484
  GStreamer | gst-plugins-good | 0.10.36

           Summary: Crash in osxvideosink when displaying on Qt widget
    Classification: Platform
           Product: GStreamer
           Version: 0.10.36
        OS/Version: Mac OS
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: 4ernov at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


I suffer some strange crash in showFrame() obj-C method of
GstOSXVideoSinkObject in osxvideosink when frames are being displayed on
external view (in my case, Qt4 widget). Crash report is attached. The good news
is that a modified example qt-overlay.c from gst-plugin-base package apparently
works fine. I'll try to get test program reproducing the crash tomorrow, but
maybe you would suggest some potential reasons meanwhile. Here's main
differences of my program compared to test program:
1. As Qt4 don't use Glib mainloop in Mac OS X I have to rotate it manually, so
effectively there're two main loops running, though Glib one seems to be
rotating only in main thread, so there should be no problems.
2. Data is streaming from appsrc and not videotestsrc.
3. I use autovideosink so window-id is set using sync handler (we discussed it
with Sebastian in bug #691421, I fixed my code according to GSTXOverlay
example). Window-id is already obtained by the time of bus message posting, so
there's no any call to Qt stuff, it's just int assignment.

Another strange fact is that _sometimes_ the program works successfully the
very first time after I rebuild and refresh osxvideosink. But second and futher
executes crash.

osxvideosink version is latest git one from 0.10 branch.

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