I am having a problem with the jpeg encoder hanging on my DM368 with gstreamer. I am running a gstreamer pipeline that encodes both h264 (full frame rate) and jpeg (once per second). Most of the time, it works fine. However, I've written a test program to create the pipeline, run it for 5 seconds, and then tear it down. This program runs in a loop (process never exits) and the jpeg encoder hangs at various iterations. I have enabled debugging inside of the gstreamer and I get a print that it is entering the codec process function and I never get the printout that it finished the process function (in the case where it fails). I've also enabled CE_DEBUG and DMAI_DEBUG but haven't seen any reason why the encoder would hang.
After I get the jpeg encoder to hang in the process function, I can terminate my program and run a very simple gstreamer pipeline that includes the jpeg encoder element and it still hangs. I've noticed that if I run a very simple pipeline with just a h264 encoder it seems to somehow reset something because the jpeg encoder starts to work again after I run a h264 pipeline.
I've read that there is a debug version of the h264 codec but couldn't find anything on a debug version of the jpeg codec. Are there any more debugging techniques that can be used to track down why this jpeg encoder just hangs?
Thanks,
Randy Scheifele