GNOME Bugzilla – Bug 687793
v4l2src: Check for obj->pool == NULL in gst_v4l2src_fill
Last modified: 2013-01-24 03:10:35 UTC
Not sure how obj->pool can be NULL unless someone called stop and can not reproduce it either, but it did happen once during a VoIP call and the backtrace lays the blame on obj->pool being NULL. (gdb) bt
+ Trace 231139
Created attachment 228302 [details] [review] v4l2src: Check for obj->pool == NULL
*** Bug 687668 has been marked as a duplicate of this bug. ***
Added log and fixed pipeline to 687668 by mistake, please get them from there.
Created attachment 228359 [details] crashing gst-debug log
Ok, tested Debarshis patch and it does fix the crash.
> Ok, tested Debarshis patch and it does fix the crash. So it doesn't crash any more, but errors out instead then?
Yes, it errors out
Alright, the pool is NULL because it has never been created, because negotiation failed. But for some reason (an asynchronous state change), the task is re-started after it has been paused. But because of bug #691986, the NEED_RECONFIGURE flag is not longer set, and it tries to create the buffer without having caps set, and so it crashes! *** This bug has been marked as a duplicate of bug 691986 ***