I've got an application that captures and encodes video using OMX apis on a DM816x, using EZSDK 5.05. If this app crashes or is terminated early with control-C, running it again always fails when attempting to create the capture (VFCC) object. Looking at the debug logs, the vfcc driver can't be created because it's in use (FVID2_EDEVICE_INUSE).
With EZSDK 5.03, this same scenario would hang, with some thread (perhaps owned by OMX) using up 100% of the CPU.
It appears that the OMX stack or capture driver don't clean up properly on an unexpected application termination. Is this a known problem? Is there a work-around?
Thanks.