Mash node in Maya scene causes crash with V-Ray

[Fredrik Averpil]

Hi,

We noticed that with a particular scene (Maya 2018.1, V-Ray 3.60.02 official build), we got a strange crash:

>>> [2018/Jan/23|15:20:08] V-Ray: V-Ray core version is 3.60.03
>>> Initializing V-Ray for Maya
>>>
>>> [2018/Jan/23|15:20:09] V-Ray: Loading plugins from "//SERVER-REDACTED/pipeline/bin/vray/builds/171010_vray_v3.60.02-official-maya2018_linux64/maya_vray/vrayplugins/libvray_*.so"
>>> [2018/Jan/23|15:20:10] V-Ray: 76 plugin(s) loaded successfully
>>> [2018/Jan/23|15:20:10] V-Ray: Finished loading plugins.
>>> Warning: V-Ray: Could not get the renderer
>>> Warning: file: /home/iruser/maya/2018/prefs/filePathEditorRegistryPrefs.mel line 4: filePathEditor: Attribute 'MASH_Audio.filename' is invalid or is not designated 'usedAsFilename'.
>>> [2018/Jan/23|15:20:11] V-Ray: Registered dynamic node vrayMultiProjection (id: 1115335/0x001104C7)
>>> [2018/Jan/23|15:20:11] V-Ray: Registered dynamic node VRayCurvature (id: 1115347/0x001104D3)
>>> [2018/Jan/23|15:20:11] V-Ray: Registered dynamic node VRayTriplanar (id: 1115362/0x001104E2)
>>> [2018/Jan/23|15:20:11] V-Ray: Registered dynamic node VRaySkinMtl (id: 1115348/0x001104D4)
>>> [2018/Jan/23|15:20:11] V-Ray: Registered dynamic node VRayPointParticleMtl (id: 1115353/0x001104D9)
>>> [2018/Jan/23|15:20:11] V-Ray: Registered dynamic node VRayStochasticFlakesMtl (id: 1115359/0x001104DF)
>>> [2018/Jan/23|15:20:11] V-Ray: Registered dynamic node VRayAlSurface (id: 1115350/0x001104D6)
>>> info:  Loaded "//SERVER-REDACTED/pipeline/bin/vray/builds/171010_vray_v3.60.02-official-maya2018_linux64/maya_root/lib/libvraymdl.so"
>>> info:  MDL SDK 2017, build 287000.5634, 12 Apr 2017, linux-x86-64-gcc4
>>> info:  Loaded library "//SERVER-REDACTED/pipeline/bin/vray/builds/171010_vray_v3.60.02-official-maya2018_linux64/maya_root/lib/libvrayfreeimage.so".
>>> Error: line 1: VRay: Could not load the Bifrost module! You will not be able to render Bifrost as isosurface or metaball. The error message is:[loadLib] dlopen failed: libbifrostapi_1_0.so: cannot open shared object file: No such file or directory
>>> Warning: cycleCheck has been disabled for Render Setup in batch mode to minimize redundant messages in the render log
>>> QWidget: Cannot create a QWidget without QApplication

It seems Maya or V-Ray attempted to show some kind of dialog/window as a result of that libbifrostapi_1_0 wasn't found.

We tracked the issue down to the node being created when clicking "Create MASH network". After having removed this node, the above errors disappeared and the render completed successfully.

Some other notes:
- We have Maya installed without Bifrost.
- Windows (Maya GUI) was able to render the scene without issues
- I also tried rendering the same scene in Maya 2018.2 without Biftost installed and with V-Ray 3.60.03 official build and I received the very same error.


Is it possible that MASH on Linux is depending on Bifrost...?
Or that V-Ray for Maya on Linux is somehow depending on Bifrost?

[t.petrov]

Is it possible that MASH on Linux is depending on Bifrost...?

No, idea but I think this is not related.

Or that V-Ray for Maya on Linux is somehow depending on Bifrost?

Yes, it is but this doesn't cause crashes, because we're loading the bifrost module dynamically and if something happens and it fails to load we just print an error and continue.

Can you give us a scene which can be used to reproduce the problem?
If not can you attach a debugger and gather a backtrace/callstack?

Just a note: the windowing system is disabled in Batch/MayaPy, so seeing Qt messages is really suspicious. This is true for both Windows and Linux.
Do you have some scripts which try to create Qt UI and they are not checking if the mode is non-interactive?

[Fredrik Averpil]

Sorry for the late reply.

I'm attaching the log and the scenes here. Open scene33.mb (which will reference scene31.mb, which includes the MASH nodes). If you delete the MASH nodes (or import them, I'm told), the issue goes away.

This is when command line rendering on Linux with Maya 2018.2 with v-Ray 3.60.04 official release.

[shaio]

Hi,
thank you for the scene and the log. I'll take a look at them and will get back to you with some more information.

[shaio]

Hi,
we were able to reproduce the issue without V-Ray being installed using Arnold only. Maybe it is an Autodesk issue and there is nothing that we can do about it and should be reported to them. Please let me know if you have some more information or if it is not reproducible with Arnold on your end.

[Fredrik Averpil]

Ok, thanks!