Maya 2017 crash on MFileIO::open with 3dtext/svg

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi
I have been trying to update our importers for maya to 2017, they are standalone C++ applications that use the maya api.
But stumbled upon a illusive crash deep within some code out of my control, which happens *sometimes* when importing files with 3DText and SVG on windows.
This crash occurs often:
Stack trace:
Stack trace: Qt5Core.dll!QUrl::isEmpty Shared.dll!TresolveFileObject::isSet Shared.dll!TresolveFileObject::isSetURI Shared.dll!TresolveFileObject::rawFullName Shared.dll!TsceneFile::fullName Shared.dll!TfileTranslator::read Shared.dll!TglobalTranslator::doReadFile Shared.dll!TfileUtil::readFile Shared.dll!TsceneOperator::openFile Shared.dll!TfileCmd::handleFileOpenFlag Shared.dll!TfileCmd::handleFlags Shared.dll!TfileCmd::handleFlags Shared.dll!TfileCmd::doCommand CommandEngine.dll!TmetaCommandPtrArray::catenate CommandEngine.dll!TminMelArgList::nextDigit CommandEngine.dll!TminMelArgList::nextDigit CommandEngine.dll!SophiaExecutable::evaluate CommandEngine.dll!TcommandEngine::executeCommand OpenMaya.dll!MGlobal::executeCommand OpenMaya.dll!MFileIO::open KERNEL32.DLL!BaseThreadInitThunk ntdll.dll!RtlUserThreadStart
When it does not crash it does give plenty of warnings and errors ie:
API error detected in S:\Maya_2017_DI\src\Maya\src\Type\fontNode.cpp at line 2017 : (kFailure): Unexpected Internal Failure API error detected in S:\Maya_2017_DI\src\Maya\src\Type\fontNode.cpp at line 2020 : (kFailure): Unexpected Internal Failure
I have attached two files with the stderr output , and a select set of environments variables in the top.
Its quite annoying as it happens on a specific machine and I am not able to reproduce the crash on my dev machine. I will also get the API error messages, but if we ignore the warnings our importer still works alright.
It does however seem like that opening the file in maya and immediately after running out importer on the file, does not trigger the crash.
Are there any known issues in this area?
Are there any possible work arounds or fixes?
Any ideas as to what where how to approach this?