In AAF SDK 1.1.4 and 1.1.5 I continually get OMStorable exceptions when processing AAF with audio tracks. Both the COM examples and the Ax examples exhibit this. I'm using CentOS 5 and CentOS 6 - so it's not isolated to one specific version of Linux or one machine.
Precondition "Object not attached" violated in routine "OMStorable::~OMStorable".
The violation occurred at line 73 in file "OMStorable.cpp".
The condition "!attached()" was false.
Symbolic stack trace.
Anybody with the same problem?
This debug-only check means that the object being deleted thinks that it's still referenced by another object. Usually this happens when an application forgets to call IAAFFile::Close() before calling the last (i.e. the one that triggers object desctruction) IAAFFile::Release().
Thanks. I came to the same conclusion and commented out the asset, but there is something else going on as it seg-faults and I'm guessing bad data from Avid's MC.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.