[Bug 695981] Segmentation fault on gst_v4l2_buffer_pool_process after sending "start-capture" signal to camerabin2 just after setting the pipeline state to PLAYING

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Mon Apr 15 16:57:35 PDT 2013


https://bugzilla.gnome.org/show_bug.cgi?id=695981
  GStreamer | gst-plugins-good | 1.x

--- Comment #7 from Olivier Crete (Tester) <olivier.crete at ocrete.ca> 2013-04-15 23:57:28 UTC ---
Created an attachment (id=241608)
 View: https://bugzilla.gnome.org/attachment.cgi?id=241608
 Review: https://bugzilla.gnome.org/review?bug=695981&attachment=241608

I think I understand this bug, what happens is that you can get a renegotiate
event between the time that

gst_base_src_start_complete() is executed and when the loop starts. The patch
that I'm proposing to revert
would then remove the reconfigure flag from the pad, which had the side effect
of never caling set_caps,
and of never creating the buffer pool.

So I suggest a different way to disable renegotiation by just doing it at the
start of the
negotiate method.

Revert "v4l2: disable renegotiation"

This reverts commit d1b26e1d594ab2b63324e43a36330475e98cdf18.

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