Maya exited with status -1

[max@mfx]

Hi,

I'm struggling with constant crashes with certain geometry. The only output from the batch render is "Maya exited with status -1". Currently it happens just at the end of irradiance pass 3 of 4 when doing a prepass with "incremental add to current file". Previously it happened on the final render. As previously said, I think it has to do with certain geometry.

Is there any way to have vray output detailed status of which object is causing issues in the terminal when doing a batch render? I already have all messages output but only get this:

[2013/Feb/8|12:39:54] V-Ray:  (Estimated time remaining:  0h  0m  4.7s): 38 % completed
[2013/Feb/8|12:39:54] V-Ray:  (Estimated time remaining:  0h  0m  4.7s): 40 % completed
[2013/Feb/8|12:39:54] V-Ray:  (Estimated time remaining:  0h  0m  5.0s): 42 % completed
[2013/Feb/8|12:39:55] V-Ray:  (Estimated time remaining:  0h  0m  5.2s): 44 % completed
[2013/Feb/8|12:39:55] V-Ray:  (Estimated time remaining:  0h  0m  5.1s): 46 % completed
// Maya exited with status -1

It crashes both in Maya and in batch mode. I'm on the latest VRay for OS X, 2.20.

Thanks,
Max

[vlado]

Can you get me any way to reproduce this here?

Best regards,
Vlado

[max@mfx]

I think it's tricky, because every time I try to render a part of the model it works just fine. But all at once just makes it crash. And I can't send you the geometry because it's confidential unfortunately.

I have tried a lot of things here already. Any tips on debuging when the irradiance map is crashing? Or a way to find incorrect geometry if that is the cause.. I have a feeling that it can have something to do with refractions also, but just a gut feeling...

[vlado]

Do you have a way of getting me a crash dump then?

Best regards,
Vlado

[vlado]

Btw as you know we can sign an NDA.

Best regards,
Vlado

[max@mfx]

I'm not sure we are allowed to share the geometry, even with a NDA unfortunately...

The crash report is attached.

vray_crash.txt.zip

[vlado]

Hm, I see. Have you tried a newer nightly or stable build?

Best regards,
Vlado

[max@mfx]

No, but I think I have found the issue! It is something I have had issues with before but that was some time ago. I think I reported it back then...

It was a texture projection node that caused the issue. When baking the (spherical) projection using the create UV tools it doesn't crash anymore!

I may be able to create a crash scene for you later, but I have to crack on with the project now!

[vlado]

Yes, if you can get me a scene at some point, it will be very helpful.

Best regards,
vlado

[max@mfx]

I jumped to conclusions to early, it doesn't seem to be that. I bet it's the crappy geometry again...

[vlado]

I'd still try a newer build Judging from the crash log, it's unlikely that is has anything to do with the scene...

Best regards,
Vlado

[Morbid Angel]

Have you tried running cleanup on that geometry? If its a static object perhaps dropping it into vrmesh could help.

[snivlem]

Do you have instanced geometry in your scene?

I get V-Ray crashing on Irradiance mapping if Maya fails to instance properly and the shader is not attached properly (it looks okay in the viewport, but it is not). Rare though.

[max@mfx]

The more I think about it the more I agree with you Vlado, it has to be the installation...

We are running OS X 10.8.2, which isn't fully supported by maya 2012, could be that. My renders work on our Linux farm which also points in that direction.

Could it be something with hyper threading? Our farm is AMD, workstations are Intel Xeon Macs.

[vlado]

From the crash log, it seems to be related to Qt and UI message processing; I don't think it has anything to do with hyperthreading.

Best regards,
Vlado