Maya crash without log file

[BurkhardRammner]

Hi,

the whole week, I have been producing using the same scene, never shutting down my computer and Maya.

Now, I had to restart my computer and thus also Maya...

and voila -> Maya crashes during scene load without any information why it does.

So, I had to revert to a much older scene. There is nothing fundamentally different between both scenes. The newer scene is just a variation of the older.

I have absolutely no time to recreate what I obviously lost now. Unfortunately, the scene is 3 GB in size, so I cannot go through the '.ma' file and delete various parts to see if it loads now. The scene just has too much in it. Especially, there are a ton of references.

Is there any trick how I could find out what goes wrong there?

thanks!

[mspeer]

Hi!

You could try Import... instead of Open Scene... to check if there are any UI related problems.

There are of course other things that could be checked but a 3GB file is difficult to handle here at the forum.

I recommend to contact Autodesk support and include some crashlog files from the user temp directory (if there are any). Also include all information like what will be displayed in Script Editor or the Maya Output Window shortly before the crash.

[BurkhardRammner]

@mspeer 

I already tried the import variant...it fails like 'open'.

There is just no message from Maya before the crash, just nothing.

I also removed every plugin...crash.

'script editor' : nothing special to see there

The **** thing just crashes and I`m getting mad...again at the end of a project..

How on earth am I supposed to find the reason for that crash in that 3 GB file and how on earth would an Autodesk employe invest his/her time ?!?!?!

[mspeer]

Hi!

Well if you contact Autodesk support...

1) You don't have to worry about confidential content, which you can't remove from the file in this case.

2) The chance to get someone to check this large file and to find the problem is much higher than here in the forum.

( Although i would be interested to check this, i currently don't have enough free time, that's why i recommended to contact Autodesk support)

[BurkhardRammner]

@mspeer 

I already had the case that my files were rejected, because it would have been too tedious to go through all the data ; }

(which I understand)

I`m not sure what you mean by 'contact Autodesk support'. Do you mean 'bug report'? Is there a web page you can refer to or do mean something like 'gold support' or alike.

However, after a fair amount of work (delete step by step all my recent actions on my file), I found that the reason for the crash is a referenced 'polyColorPerVertex' node which got its vertex colors edited. So, this is clearly a bug, but I have no idea how I could report that (3GB)...

[mspeer]

Hi!

Sure, it can be rejected or at least the troubleshooting will be stopped after some time.

Still i think the chance is higher to get any help there than here.

If you know what's causing the problem i recommend to make this reproducible with a smaller file and report this then as bug to Autodesk.

[BurkhardRammner]

It looks like the crash happens only with big polyColorPerVertex edits.

[mspeer]

Hi!

If a scene contains only one "big" object it should still be smaller than 3 GB.

You can also provide procedural steps like.

1. Create a poly primitive with x subdivisions (or even directly add the MEL command)

2. then....

This way you don't have to attach any scene-file to a bug report.

[BurkhardRammner]

mspeer,

currently, I have absolutely no time to test for a minimum file I could send AD.

And as already said, the bug appears only when the data are large enough.

If I would take together the total time I used to find the source for bugs, create a minimal file and send that to AD, I would have the equivalent of a life-long Maya license.

[mspeer]

Hi!

"If I would take together the total time I used to find the source for bugs, create a minimal file and send that to AD, I would have the equivalent of a life-long Maya license."

- I totally understand this and you are for sure not the only one who spent a lot of time on preparing bug reports.

Currently i don't see any further option i could offer here.