Forum Post: DM814x: gStreamer crashing for 1080i on DM814x

Hi,
I am trying a transcoding pipeline at 1080i resolution on DM814x.
This is my gStreamer pipeline command.

gst-launch-0.10  filesrc location=/media/mmcblk0p1/streams/MPEG2-1080i-12mbps-AC3-48-128.ts typefind=true ! mpegtsdemux ! mpegvideoparse ! omx_mpeg2dec ! omx_mdeiscaler name=d d.src_01 ! 'video/x-raw-yuv,format=(fourcc)NV12, width=1920,height=1080' ! omx_h264enc ! mpegtsmux ! filesink location=/media/mmcblk0p1/streams/mpge2i-h264p1080.ts

But I am getting the bellow error. But if I run it for lower resolutions say 720/480i it works fine,
even for 1080p it works fine, but crashes only if I use De-Interlacer i.e. 1080i

Error:
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
this input  params: 1920x540,1920 3110400 1
incoming buffer: nFilledLen: 3133440, nOffset: 0 nFlags: 10200
OMX_EventError: 0x80001000
unrecoverable error: There were insufficient resources to perform the requested operation (0x80001000)
ERROR: from element /GstPipeline:pipeline0/GstOmxH264Enc:omxh264enc0: GStreamer encountered a general stream error.
Additional debug info:
gstomx_base_filter.c(708): pad_chain (): /GstPipeline:pipeline0/GstOmxH264Enc:omxh264enc0:
Error from OpenMAX component
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
OMX_EventError: 0x80001001
unrecoverable error: The cause of the error could not be determined (0x80001001)
Freeing pipeline ...

(gst-launch-0.10:1368): GStreamer-CRITICAL **:
Trying to dispose element d, but it is in PAUSED instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(gst-launch-0.10:1368): GStreamer-CRITICAL **:
Trying to dispose element omxmpeg2dec0, but it is in PAUSED instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.

Assertion at Line no: 380 in /u/users/tejaswini/DESAY_MRL/dst_sdk/component-sources/syslink/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/utils/hlos/knl/ResTrack.c: (elem == NULL) : failed
Assertion at Line no: 380 in /u/users/tejaswini/DESAY_MRL/dst_sdk/component-sources/syslink/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/utils/hlos/knl/ResTrack.c: (elem == NULL) : failed