Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

Unity 2018.3b9 Windows standalone crash on first run - UnityPlayer.dll caused an Access Violation

Discussion in '2018.3 Beta' started by Lauwisme, Nov 11, 2018.

  1. Lauwisme

    Lauwisme

    Joined:
    Apr 1, 2014
    Posts:
    2
    I'm trying to build a project but every build crashes the player instantly.

    The error and output logs are included.

    UnityPlayer.dll caused an Access Violation (0xc0000005)
    in module UnityPlayer.dll at 0033:6eb5d326.

    Error occurred at 2018-11-11_082820.
    C:\Users\laurent\Documents\Development\Projects\P_Academie\Builds\CarChase\B-VR-CarChase.exe, run by laurent.

    71% physical memory in use.
    16344 MB physical memory [4709 MB free].
    506 MB process peak paging file [502 MB used].
    236 MB process peak working set [232 MB used].
    System Commit Total/Limit/Peak: 22827MB/32688MB/31668MB
    System Physical Total/Available: 16344MB/4709MB
    System Process Count: 334
    System Thread Count: 4690
    System Handle Count: 158104
    Disk space data for 'C:\Users\laurent\AppData\Local\Temp\B\B-VR-CarChase\Crashes\Crash_2018-11-11_072817954\': 29675634688 bytes free of 249427914752 total.

    Read from location 0000000000000208 caused an access violation.

    Context:
    RDI: 0x00000172b55c5df0 RSI: 0x00000172969eead0 RAX: 0x00007ffa6f60d9a0
    RBX: 0x00000172b55c5df0 RCX: 0x0000000000000000 RDX: 0x0000000000000004
    RIP: 0x00007ffa6eb5d326 RBP: 0x00007ffa6f565000 SegCs: 0x0000000000000033
    EFlags: 0x0000000000010206 RSP: 0x000000639453ed30 SegSs: 0x000000000000002b
    R8: 0x0000000000000010 R9: 0x00007ffa6e3d0000 R10: 0x00000172969e6dd8
    R11: 0x0000017296e5ada8 R12: 0x0000000000000000 R13: 0x00000172b2c9d400
    R14: 0x0000000000000006 R15: 0x00000172b25af9c0


    Bytes at CS:EIP:
    0f 10 81 08 02 00 00 48 8b d9 0f 29 44 24 20 e8

    Mono DLL loaded successfully at 'C:\Users\laurent\Documents\Development\Projects\P_Academie\Builds\CarChase\MonoBleedingEdge\EmbedRuntime\mono-2.0-bdwgc.dll'.

    I've tried all the usual things: check folder permissions, disable antivirus, update graphics drivers, check folder permissions but nothing has worked so far.

    Could it have something to do with these shaders?

    WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader
    WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader
    WARNING: Shader Unsupported: 'Standard (Specular setup)' - Pass 'META' has no vertex shader
    WARNING: Shader Unsupported: 'Standard (Specular setup)' - Pass 'META' has no vertex shader
    WARNING: Shader Unsupported: 'Nature/SpeedTree' - Pass 'Meta' has no vertex shader
    WARNING: Shader Unsupported: 'Nature/SpeedTree' - Pass 'Meta' has no vertex shader
    UnloadTime: 0.539000 ms
    Crash!!!
    SymInit: Symbol-SearchPath: '.;C:\Users\laurent\Documents\Development\Projects\P_Academie\B-VR-CarChase;C:\Users\laurent\Documents\Development\Projects\P_Academie\Builds\CarChase;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 534, UserName: 'laurent'
    OS-Version: 10.0.0

    I'm not that experienced looking into these logfiles, so I wonder if someone from the Unity team could point me in the right direction?

    Thanks,
    Laurent
     

    Attached Files:

    Lauwisme, Nov 11, 2018
    #1

  2. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,674
    Your crash zip file is missing the .dmp file. Can you upload that?
     
    Tautvydas-Zilys, Nov 11, 2018
    #2

  3. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,674
    Thanks for the dump file. Here's the reconstructed callstack:

    Code (csharp):
    1. UnityPlayer.dll!MeshAsyncUpload::SyncForMainThread(MeshAsyncUpload::UploadInstruction * instr)
    2. [Inline Frame] UnityPlayer.dll!Mesh::CompleteUploadCommand()
    3. UnityPlayer.dll!Mesh::AwakeFromLoad(AwakeFromLoadMode awakeMode)
    4. UnityPlayer.dll!Mesh::GetInstantiatedMesh(Mesh * mesh, Object & owner)
    5. [Inline Frame] UnityPlayer.dll!MeshFilter::GetInstantiatedMesh()
    6. UnityPlayer.dll!MeshFilter::GetInstantiatedMeshFromScript()
    7. UnityPlayer.dll!MeshFilter_Get_Custom_PropMesh(MonoObject * _unity_self)
    This gets triggered by one of your scripts calling into mesh property on a mesh filter. Unfortunately the mini-dump didn't contain enough information for me to figure out which script is doing it.

    This is definitely a bug in Unity, however, we will need a full bug report in order to be able to fix it.
     
    Tautvydas-Zilys, Nov 13, 2018
    #3

  4. IJsLauw

    IJsLauw

    Joined:
    May 31, 2015
    Posts:
    15
    Thanks for looking into it.

    By process of elimination we were able to remove the gameobject that was causing the problem. Now we can build the project again, so we're happy, but now I can't file a full bug report anymore.

    Next time something like this happens I'll be sure to report it.
     
    IJsLauw, Nov 14, 2018
    #4