Semi-reproducible crash in Maya 2018.4

[Anonymous]

I've found a semi-reproducible crash in Maya 2018.4 and I haven't found any other posts on it in a brief look around the forums. I say "semi-reproducible" because the crash occurs within 5-15 minutes of working on this particular project file but I cannot find an exact step that causes the crash. It's kind of strange. 

Basically I've been rigging this character for work and, after some point, Maya 2018.4 crashes consistently and repeatedly, no matter what I do (changing workflow, not using Undo, disabling plugins, etc). This crash does NOT occur with Maya 2017 so that's what I've been using to get my work done, but I figure it's a good idea to bring this up so that it can get fixed in follow-up releases. I'm also curious what the actual problem is, as I haven't been able to figure it out. 

I'm attaching some crash logs. I have many more. I can't post the actual scene file but I could probably provide it privately if necessary. I can't seem to attach the crash dmp file for whatever reason.... Not sure what's going on there. Also, worth noting that all my drivers are up to date, etc etc.

[sean.heasley]

Hi @Anonymous

Thanks for the info and crash log!

When your Maya is crashing, is it generating a report to fill out and submit to Autodesk? If so, please fill it out and let me know what the CER report number is so I can look it up in our system.

Also, a quick test you can try is to export everything from that scene file as an fbx then import it into a fresh empty scene file and continue to work and see if the crash occurs again.

Let me know if anything changes!

[Anonymous]

It did submit with a CER # but I only get the crash notification window (and submission form) about 10% of the time it crashes (the rest of the time it just hangs and then closes). I'll try to reproduce it but I'm not entirely positive that it will reproduce with a CER in a short period of time. When I submitted it I did provide my email address so perhaps you can look it up that way?

I haven't bothered to export to FBX as I wasn't sure that would maintain all my constrants and all that nonsense. 2017 is working okay for now, I just wanted to bring it up to make sure it gets fixed for the next release. I also have a multitude of .DMP files if those would be of value.

[sean.heasley]

Hi @Anonymous

I was able to look up your crashes by email but they aren't currently linked to any known issues.

Out of curiosity, are you able to test this file on either vanilla Maya 2018 and/or Maya 2017 to see if the same crash occurs?

Also, when you get a chance can you please zip and attach the scene file here or via dropbox/google drive or another file sharing program so I can take a look at it? If the file is confidential or under NDA please send it to me in a private message instead of posting it here.

[Anonymous]

Okay, I sent you the file. 

As I mentioned earlier, Maya 2017 does NOT crash. I'm not sure about stock 2018 as I haven't reinstalled it yet, but it's clearly a regression at some point.

Let me know if you figure out the provenance of the crash. I'm pretty curious at this point!

[sean.heasley]

Hi @Anonymous

Thanks for sending me the file!

I wasn't able to reproduce the crash, however I believe this issue is similar to another crash I logged with our dev team a few weeks ago. I went ahead and update that log with this thread so the devs have all this information and can add it to their fix.

Please let me know if anything changes or if you find more repro steps and I'll update the report for them!

[sean.heasley]

Also since 2017 is working ok for you, I recommend making a backup of your work and then try the export/import into a fresh 2018 scene just to see if this still occurs.

[Anonymous]

I'm surprised you can't reproduce it... That's really really weird. This is like a 100% of the time crash for me. Weird...

Worth noting, though, that I did try what you suggest: I exported the entire scene, reimported it into a blank scene (and fixed the namespaces) and the crash still occurred. This was all in 2018 (never exported from 2017 to 2018, maybe I'll try that next) but export/reimport within 2018 did NOT fix it.

[sean.heasley · Accepted solution]

Hi @Anonymous

Thanks for that info! I'll be sure to update the report on this issue with this new information!