[Bug 730167] panic in gst_bin_continue_func() when doing continuous zap operations

[GStreamer (bugzilla.gnome.org)]

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

--- Comment #2 from bcxa.sz at gmail.com 2014-05-15 05:28:41 UTC ---
And why sometimes the panic happen, I thought:

The pipeline has been changed from PLAYING to NULL and unref before the
gst_bin_continue_func() want to commit the state from PAUSED to PLAYING. 

Look at gdb_backtrace.log: We can see
======================================================
current_state = GST_STATE_NULL, 
next_state = GST_STATE_VOID_PENDING, 
pending_state = GST_STATE_VOID_PENDING, 
last_return = GST_STATE_CHANGE_SUCCESS
and many members are 0 and even name is '\0'. This piece of code can be found
in gst_element_finalize() and gst_object_finalize().
======================================================

And it maybe due to thread schedule, gst_bin_continue_func() is just called
later than the operation to change pipeline from PLAYING to NULL then unref.
Then it try to access the element which has been freed then segmentation
happen.

Do you think what I thought make sense? If yes, how to resolve such kind of
issue?

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