Maya Crash

V-Ray for Maya V-Ray for Maya :: Issues
1

Having a few crashes mid render at the mo.

The GI is calculated and the buckets start to render, but about a quarter of the way through, Maya quits:
The scene renders ok with simple spheres, but as soon as I switch on the CAD data, the scene crashes mid way through the render.

Using:
Maya 2016.5 Ext 2
Vray build: // Result: 27471
3.6 stable

Here’s a few lines from the crash:
-------------------------------------------------------------------------------------------------------------------------------------
Process: Maya [26060]
Path: /Applications/Autodesk/*/Maya.app/Contents/MacOS/Maya
Identifier: com.autodesk.Maya.2016.5
Version: Maya 2016.5 (2016.5)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Maya [26060]
User ID: 1863960546

Date/Time: 2017-06-28 12:44:01.353 +0100
OS Version: Mac OS X 10.12.5 (16F73)
Report Version: 12
Anonymous UUID: 57D2380F-B08A-6649-807C-AAF2C0FF0BEF

Sleep/Wake UUID: 519C22C3-3138-4151-A291-8DBFFF2ECFFA

Time Awake Since Boot: 180000 seconds
Time Since Wake: 14000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: Maya [26060]

-------------------------------------------------------------------------------------------------------------------------------------

Cheers

2

Hi,
there might be some corrupted CAD geometry or something else that is causing the crash. If possible sharing the scene and full log will be very helpful for us. I’ll try some scenes with CAD geometry and see if it reproduces here then get back to you with some more info.

3

Cool cheers.
How do I go about saving out a full log on a mac?

I’m not going to be able to send the scene on this one.

Just so you know, I tried saving out proxies and Maya still crashed.
I’ll work through the scene to find the culprit.

4

Stripped down the scene to the piece of geometry that was causing the issue (or so I thought).
Deleted this piece from the scene, but have the same crash/Maya vanish.

5

Tried on larger drive, as thought this might be a HD space issue.

6

I’m making some tests here but without any success on reproducing the crash. I’ll keep trying and will let you know if I find something.
If you start Maya from the terminal by using the following command “/Applications/Autodesk/maya2016.5/Maya.app/Contents/MacOS/Maya” will start Maya from the terminal and use it as a console output. When the crash occurs there will be some crash log data in the terminal. Copy it and share it here so we can see if there is any helpful information for debugging.

7

Cool. Here’s the terminal output up to where Maya pops/disppears:

[2017/Jun/29|11:42:00] V-Ray: (Estimated time remaining: 0h 0m 30.8s): 10 % completed

[2017/Jun/29|11:42:01] V-Ray: (Estimated time remaining: 0h 0m 17.2s): 20 % completed

[2017/Jun/29|11:42:02] V-Ray: (Estimated time remaining: 0h 0m 11.2s): 32 % completed

[2017/Jun/29|11:42:03] V-Ray: (Estimated time remaining: 0h 0m 8.5s): 42 % completed

[2017/Jun/29|11:42:03] V-Ray: (Estimated time remaining: 0h 0m 6.5s): 51 % completed

[2017/Jun/29|11:42:04] V-Ray: (Estimated time remaining: 0h 0m 4.9s): 61 % completed

[2017/Jun/29|11:42:05] V-Ray: (Estimated time remaining: 0h 0m 3.5s): 70 % completed

[2017/Jun/29|11:42:06] V-Ray: (Estimated time remaining: 0h 0m 2.3s): 80 % completed

[2017/Jun/29|11:42:07] V-Ray: (Estimated time remaining: 0h 0m 1.1s): 90 % completed

[2017/Jun/29|11:42:08] V-Ray: Merging light cache passes…

[2017/Jun/29|11:42:08] V-Ray: (Estimated time remaining: 0h 0m 0.1s): 12 % completed

[2017/Jun/29|11:42:08] V-Ray: (Estimated time remaining: 0h 0m 0.9s): 23 % completed

[2017/Jun/29|11:42:08] V-Ray: (Estimated time remaining: 0h 0m 1.2s): 38 % completed

[2017/Jun/29|11:42:08] V-Ray: (Estimated time remaining: 0h 0m 1.2s): 41 % completed

[2017/Jun/29|11:42:08] V-Ray: (Estimated time remaining: 0h 0m 0.9s): 50 % completed

[2017/Jun/29|11:42:09] V-Ray: (Estimated time remaining: 0h 0m 0.7s): 61 % completed

[2017/Jun/29|11:42:09] V-Ray: (Estimated time remaining: 0h 0m 0.5s): 74 % completed

[2017/Jun/29|11:42:09] V-Ray: (Estimated time remaining: 0h 0m 0.2s): 88 % completed

[2017/Jun/29|11:42:10] V-Ray: (Estimated time remaining: 0h 0m 0.0s): 100 % completed

[2017/Jun/29|11:42:10] V-Ray: Light cache contains 44962 samples.

[2017/Jun/29|11:42:10] V-Ray: Light cache base memory usage is 12.5 MB.

[2017/Jun/29|11:42:10] V-Ray: Prefiltering light cache…

[2017/Jun/29|11:42:10] V-Ray: Average rays per light cache sample: 14.72 (min 1, max 425)

[2017/Jun/29|11:42:10] V-Ray: Using premultiplied light cache.

[2017/Jun/29|11:42:10] V-Ray: Rendering image…

[2017/Jun/29|11:42:10] V-Ray: (Estimated time remaining: 0h 0m 5.1s): 10 % completed

[2017/Jun/29|11:42:11] V-Ray: (Estimated time remaining: 0h 0m 3.5s): 22 % completed

[2017/Jun/29|11:42:12] V-Ray: (Estimated time remaining: 0h 0m 3.5s): 35 % completed

[2017/Jun/29|11:42:12] V-Ray: (Estimated time remaining: 0h 0m 3.2s): 40 % completed

[2017/Jun/29|11:42:19] V-Ray: (Estimated time remaining: 0h 0m 8.7s): 50 % completed

[2017/Jun/29|11:42:25] V-Ray: (Estimated time remaining: 0h 0m 10.0s): 60 % completed

Illegal instruction: 4

8

Bringing in previous CAD solves the issue, so there must have been some corruption in the geo.

9

Spoke too soon. As soon as I replace a shader and render:

[2017/Jun/29|14:03:59] V-Ray: (Estimated time remaining: 0h 0m 21.4s): 50 % completed
Segmentation fault: 11

10

Ok. The shader used a switch material.
I replaced this switch material with a shader directly.

Things seem to be ok…for now.

11

So there is something in the switch material. That is a great hint, I’ll try it and get back to you with some more info.

12

I made quite a lot of tests with different cad geometry and SwitchMtl without any luck on reproducing. Can you tell me what kind of materials you have inside the SwittchMtl? Is the Switch parameter on the materials mapped or animated? If the issue is caused by some of the materials attached to the switch material can you isolate the exact material that causes the crash?

13

Hi Ivan

Thanks for all the tests.

I’m back in work next week, so will be able to confirm, but I think it was a VRay Carpaint, a silver VRScan and a red VRScan.

Cheers

14

Ok I’ll try it out and let you know if I have any success. When you have a chance It will be very useful to tell me the names of the vrscan files you use so I could use those files too.

15

We are using:
carpaint_grey_1_e.vrscan
carpaint_red_4_s.vrscan

Cheers

16

Thanks, I’ll test them and get back to you with more details.

17

Is the switch value in the SwitchMtl mapped or animated (if you’re trying to render more than one frame)? Sharing your render settings (as preset maybe) could also be very helpful.

18

Hi Ivan

Sorry for the delay.

The switch value isn’t animated or mapped, from checking.

I’ve PM the render settings.

Cheers

19

Ok, thanks for PM-ing the render settings. I’ll apply them and make some more tests and hopefully it reproduces the issue.

20

Hi,
still no success on reproducing it here. Is it possible to share the scene stripped without the CAD geometry or anything that can’t be shared? Also could you please try assigning the scanned materials directly to the geometry without using the switch material.