Search Unity

iOS crashes in CreateMetalShaderShaderLab

Discussion in 'iOS and tvOS' started by liortal, Sep 15, 2017.

  1. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    We just upgraded our project to use Untiy 5.6.3p2 and we are seeing a high number of these crashes. These happen pretty early in the game, we assume at the point where the game loads assets from an asset bundle.

    I could not find any reported by similar to this. Has anyone else seen this kind of crashes ? how can we resolve it ?

    Code (CSharp):
    1. 0    coinmaster    CreateMetalShaderShaderLab(ShaderGpuProgramType, dynamic_array<unsigned char, 1ul> const&) (in coinmaster) (MetalShaderBlobHeader.h:39)
    2. 1    coinmaster    CreateGpuProgram(ShaderGpuProgramType, dynamic_array<unsigned char, 1ul> const&, CreateGpuProgramOutput&) (in coinmaster) (GpuProgram.cpp:866)
    3. 2    coinmaster    CreateGpuProgramQueue::DequeueAll(GfxThreadableDevice*) (in coinmaster) (GfxDeviceWorker.cpp:2182)
    4. 3    coinmaster    GfxDeviceWorker::RunCommand(ThreadedStreamBuffer&) (in coinmaster) (GfxDeviceWorker.cpp:653)
    5. 4    coinmaster    GfxDeviceWorkerAutoreleasePoolProxy (in coinmaster) (GfxDeviceMetal.mm:2848)
    6. 5    coinmaster    GfxDeviceWorker::Run() (in coinmaster) (GfxDeviceWorker.cpp:355)
    7. 6    coinmaster    GfxDeviceWorker::RunGfxDeviceWorker(void*) (in coinmaster) (GfxDeviceWorker.cpp:329)
    8. 7    coinmaster    Thread::RunThreadWrapper(void*) (in coinmaster) (Thread.cpp:35)
    9. 8    libsystem_pthread.dylib    0x18f65d68c 0x18f65a000 + 13964
    10. 9    libsystem_pthread.dylib    0x18f65d59c 0x18f65a000 + 13724
    11. 10    libsystem_pthread.dylib    0x18f65acb4 0x18f65a000 + 3252
     
    liortal, Sep 15, 2017
    #1

  2. christophergoy

    christophergoy

    Joined:
    Sep 16, 2015
    Posts:
    735
    do you have a full crash log? Also, have you been able to reproduce it locally? Any more information would be helpful.
     
    christophergoy, Sep 16, 2017
    #2

  3. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    Yes, we can reproduce it locally. should i post the crashreport as well ? (you mean the actual .crashreport file right?)
     
    liortal, Sep 16, 2017
    #3

  4. christophergoy

    christophergoy

    Joined:
    Sep 16, 2015
    Posts:
    735
    Yes, do you also know which shader is causing the issue?
     
    christophergoy, Sep 16, 2017
    #4

  5. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    no, i have no idea. the error doesn't mention that. we do not have custom shaders. using the built-in ones.
     
    liortal, Sep 16, 2017
    #5

  6. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    Attaching the symbolicated crash report. let me know if you need any more information, or whether i should report this as a bug.
     

    Attached Files:

    liortal, Sep 17, 2017
    #6

  7. christophergoy

    christophergoy

    Joined:
    Sep 16, 2015
    Posts:
    735
    Please report a Bug :)
     
    christophergoy, Sep 17, 2017
    #7

  8. SamiSdd

    SamiSdd

    Joined:
    Mar 12, 2015
    Posts:
    11
    @liortal were you able to fix this?
     
    SamiSdd, Jul 12, 2018
    #8

  9. liortal

    liortal

    Joined:
    Oct 17, 2012
    Posts:
    3,562
    The issue (if i remember correctly) had to do with compatibility of asset bundles and the Unity version the actual game was built with.

    In our case, asset bundles were built in Unity 5.5.3p1, but the game was built with 5.6.3p2.
    This caused the particular crash.

    Here is the response i got from Unity after reporting this bug:
    upload_2018-7-13_8-49-50.png
     
    liortal, Jul 13, 2018
    #9