GNOME Bugzilla – Bug 729855
[RPI] Errors stopping gst-launch-1.0 with ctrl+C
Last modified: 2014-06-24 12:57:03 UTC
Running a fresh master build of core/base/good/bad/ugly/omx as gst-uninstalled I can reproduce the following. gst-launch-1.0 filesrc location= ~/media/big_buck_bunny_720p_h264.mov ! qtdemux ! h264parse ! omxh264dec ! queue ! glimagesink enable-last-sample=0 Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Got context from element 'glimagesink0': gst.gl.GLDisplay=context, gst.gl.GLDisplay=(GstGLDisplay)"\(GstGLDisplayEGL\)\ gldisplayegl0"; Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock ^Chandling interrupt. Interrupt: Stopping pipeline ... Execution ended after 0:00:02.427040105 Setting pipeline to PAUSED ... Setting pipeline to READY ... 0:00:03.553737590 2493 0xffeb00 ERROR omx gstomx.c:834:gst_omx_component_set_state:<omxh264dec-omxh264dec0> Error setting video_decode state from 3 to 2: Insufficient resources (0x80001000) 0:00:08.557713149 2493 0x120c420 ERROR omx gstomx.c:524:EventHandler:<omxh264dec-omxh264dec0> video_decode got error: Incorrect state transition (0x80001017) 0:00:08.559278069 2493 0xffeb00 ERROR omx gstomx.c:260:gst_omx_component_handle_messages:<omxh264dec-omxh264dec0> video_decode got error: Incorrect state transition (0x80001017) 0:00:08.560501007 2493 0xffeb00 ERROR omx gstomx.c:1751:gst_omx_port_deallocate_buffers_unlocked:<omxh264dec-omxh264dec0> Component video_decode in error state: Incorrect state transition (0x80001017) 0:00:08.563056876 2493 0x120c420 ERROR omx gstomx.c:524:EventHandler:<omxh264dec-omxh264dec0> video_decode got error: Port unpopulated (0x8000101c) 0:00:08.571974421 2493 0xffeb00 ERROR omx gstomx.c:260:gst_omx_component_handle_messages:<omxh264dec-omxh264dec0> video_decode got error: Port unpopulated (0x8000101c) 0:00:08.816461940 2493 0xffeb00 ERROR omx gstomx.c:1150:gst_omx_close_tunnel:<omxh264dec-omxh264dec0> Failed to close tunnel on output side Incorrect state operation (0x80001018) 0:00:08.818440839 2493 0xffeb00 ERROR omx gstomx.c:861:gst_omx_component_get_state:<omxh264dec-omxh264dec0> Component video_decode in error state: Incorrect state transition (0x80001017) 0:00:08.819798770 2493 0xffeb00 ERROR omx gstomx.c:861:gst_omx_component_get_state:<omxh264dec-omxh264dec0> Component video_decode in error state: Incorrect state transition (0x80001017) 0:00:08.820991709 2493 0xffeb00 ERROR omx gstomx.c:834:gst_omx_component_set_state:<omxh264dec-omxh264dec0> Error setting video_decode state from 3 to 1: Incorrect state transition (0x80001017) Setting pipeline to NULL ... 0:00:08.830108244 2493 0xffeb00 ERROR omx gstomx.c:861:gst_omx_component_get_state:<omxh264dec-omxh264dec0> Component video_decode in error state: Incorrect state transition (0x80001017) 0:00:08.831135191 2493 0xffeb00 ERROR omx gstomx.c:834:gst_omx_component_set_state:<omxh264dec-omxh264dec0> Error setting video_decode state from 3 to 1: Incorrect state transition (0x80001017) It seems some sort of race because I don't see it always but doesn't seems to be hard to reproduce. The RPI is running raspbian with latest available firmware updated via rpi-update. The RPI is overclocked to 900MHz. This seems a regression with respect eglglimagesink.
I've tried with some other clips and I couldn't reproduce it so the issue might be related to this [1] specific clip. Maybe something changed elsewhere in GStreamer that triggered the issue as I've been using this clip several months in the RPI to test gst-omx. [1] https://dl.dropboxusercontent.com/u/4577541/big_buck_bunny_720p_h264.mov
Can you get a backtrace of all threads when it is blocking when shutting down the pipeline?
Today I had a try but I was not able to reproduce the problem mentioned in #1. Though my config is a bit risky at the moment, all gst1.2.0 except gst-omx (upstream bit reverting the recent release_frame commit) and upstream gstgl+glimagesink.