Thank you for submitting your inquiry.
You can track the status of your inquiry here.
You may want to save your case's ticket: 932027_igvaoalmth08df4l

    (Closed) 5.6+ Crash with GPU Rendering on AWS
    5.6+ Crash with GPU Rendering on AWS

    I have been running a Unity 5.5.x based application that relies on rendering on AWS using Nvidia GPU nodes (e.g. p2.xlarge or g2.2xlarge) without a physical display for a while now with good results. I'd like to upgrade to Unity 5.6 or 2017.1, but since version 5.6 (and including 2017.1) my application crashes while starting up.

    My configuration includes an AWS p2.xlarge or g2.2xlarge instance, Ubuntu 16.04 LTS, the latest Nvidia driver (375.x), and X11. I execute my application using the -batchmode parameter, although I'm not sure if that is required.

    To duplicate this crash, you need to only build a default, empty project for Linux x86_64 or Linux x86 (attached). You will find that when built with Unity 5.5.x, the application will run normally, but it will crash if built with Unity 5.6 or later. The stack trace that I see with both the latest 5.6.x patch release and the 2017.1 release is shown below.  To see these results, I believe it is important to run on an AWS node (or very similiarly configured headless configuration with an Nvidia GPU) and not a desktop / laptop with a display.

    Note that I am using a very similar approach to what is described in this blog:
    If you use the AMI and application referenced in the blog, you will get similar results (e.g. it will work with Unity 5.5.x but not with 5.6.x or 2017.1).


    Native stacktrace:

            /home/ubuntu/linuxbatchmodecrash_Data/Mono/x86_64/ [0x7f2355d28c4d]
            /lib/x86_64-linux-gnu/ [0x7f2358daa32f]
            /lib/x86_64-linux-gnu/ [0x7f2357fe3c37]
            /lib/x86_64-linux-gnu/ [0x7f2357fe7027]
            ./linuxbatchmodecrash.x86_64() [0x9f627b]
            /home/ubuntu/linuxbatchmodecrash_Data/Mono/x86_64/ [0x7f2355d67cb2]
            /home/ubuntu/linuxbatchmodecrash_Data/Mono/x86_64/ [0x7f2355ccba7d]
            /lib/x86_64-linux-gnu/ [0x7f2358daa32f]
            ./linuxbatchmodecrash.x86_64(SDL_GL_GetAttribute_REAL+0x1e3) [0x13b47e3]
            ./linuxbatchmodecrash.x86_64() [0x125d447]
            ./linuxbatchmodecrash.x86_64() [0x125bea8]
            ./linuxbatchmodecrash.x86_64() [0x125bf58]
            ./linuxbatchmodecrash.x86_64() [0x122cc0b]
            ./linuxbatchmodecrash.x86_64() [0x454b0b]
            /lib/x86_64-linux-gnu/ [0x7f2357fcef44]
            ./linuxbatchmodecrash.x86_64() [0x45df08]

    Debug info from gdb:

    Got a SIGABRT while executing native code. This usually indicates
    a fatal error in the mono runtime or one of the native libraries
    used by your application.

     > >, std::allocator<std::pair<core::basic_string<char, core::StringStorageDefault<char> > const, bool> > >::~map()
    #5  0x007fff649772e0 in std::map<core::basic_string<char, core::StringStorageDefault<char> >, core::basic_string<char, core::StringStorageDefault<char> >, std::less<core::basic_string<char, core::StringSto
    rageDefault<char> > >, std::allocator<std::pair<core::basic_string<char, core::StringStorageDefault<char> > const, core::basic_string<char, core::StringStorageDefault<char> > > > >::~map()
    #6  0x007fff64977340 in zcfree
    #7  0x007fff64978170 in __libc_start_main
    #8  0x007fff64978230 in zcfree

    License type: Pro
      To follow up on this case, send email to mentioning 'Case 932027' in the subject.
      Your Cases:
      Case Title Status Date Opened
      932027 5.6+ Crash with GPU Rendering on AWS Closed 7/17/2017 11:20 PM
      914015 Batch Mode Causes Crash in Linux for Unity 5.6 Open 5/23/2017 8:50 PM