Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We’re making changes to the Unity Runtime Fee pricing policy that we announced on September 12th. Access our latest thread for more information!
    Dismiss Notice
  3. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Important updates to the Unity Runtime Fee policy Unite 2023 Registrations are now LIVE!

Bug Apple Silicon 2021.2.0b9 + macOS 12b6 | Shader compiler crashes when opening any project

Discussion in '2021.2 Beta' started by DrewFitz, Sep 1, 2021.

  1. DrewFitz

    DrewFitz

    Joined:
    Dec 9, 2016
    Posts:
    30
    I've been using the Apple Silicon preview editor on Monterey since it released with relatively few issues. But today I can't open any projects, even fresh, empty built-in render pipeline projects with the AS preview editor. The 2020 LTS editor seems to be fine.

    As I was writing this, I downloaded the Intel version of 2021.2.0b9 and verified that it launches successfully.
     
    DrewFitz, Sep 1, 2021
    #1

  2. aleksandrk

    aleksandrk

    Unity Technologies

    Joined:
    Jul 3, 2017
    Posts:
    2,818
    Please submit a bug report - we'll investigate.
     
    aleksandrk, Sep 1, 2021
    #2

  3. DrewFitz

    DrewFitz

    Joined:
    Dec 9, 2016
    Posts:
    30
    Submitted: Case 1361979
     
    DrewFitz, Sep 1, 2021
    #3
    aleksandrk likes this.

  4. Fitts

    Fitts

    Joined:
    Jul 6, 2017
    Posts:
    3
    For anyone affected by this that doesn't want to use the full Intel version of the editor, as a workaround you can replace some of the arm64 executables and libraries in the Apple Silicon editor package /Contents/Tools/ with their equivalent versions from an Intel install, and just letting those specific tools that aren't working in beta 6 run under Rosetta instead of the entire editor. Replacing the following four files got it to work for me:

    -UnityShaderCompiler
    -D3Dcompiler_47.dll
    -gslang.dylib
    -libdxcompiler.dylib

    There might be a few things that aren't working that I haven't run into yet, but this is enough to get my project open and running and building.
     
    Last edited: Sep 3, 2021
    Fitts, Sep 3, 2021
    #4
    DrewFitz likes this.

  5. DrewFitz

    DrewFitz

    Joined:
    Dec 9, 2016
    Posts:
    30
    Thanks for the workaround! It works!
     
    DrewFitz, Sep 6, 2021
    #5

  6. DrewFitz

    DrewFitz

    Joined:
    Dec 9, 2016
    Posts:
    30
    Verified that this issue still persists in beta 10.
     
    DrewFitz, Sep 6, 2021
    #6

  7. DrewFitz

    DrewFitz

    Joined:
    Dec 9, 2016
    Posts:
    30
    Verified that this issue still persists in beta 11.
     
    DrewFitz, Sep 9, 2021
    #7

  8. sk0g

    sk0g

    Joined:
    Mar 5, 2021
    Posts:
    33
    With the above workaround, anyone else getting random crashes? I get it when dealing with heavy inspector changes (particles), as well as when exiting play mode at times. Unity just hangs up and I have to force quit it to get going again.
     
    sk0g, Sep 15, 2021
    #8

  9. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,423
    I just finished implementing the fix today. Hoping to get it in soon.
     
    Tautvydas-Zilys, Sep 18, 2021
    #9
    DrewFitz and sk0g like this.

  10. sk0g

    sk0g

    Joined:
    Mar 5, 2021
    Posts:
    33
    Amazing news! Excited to check it out, appreciate the effort that's been going into as small a market as M1 Macs may be right now.

    Is the issue related so some changed VM handling in beta 6? JetBrains IDEs broke with this beta too, but they haven't addressed or fixed it yet.
     
    sk0g, Sep 18, 2021
    #10

  11. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,423
    Nah, we were accidentally using the x18 register in our assembly code which is apparently reserved on Apple silicon (and Monterey started using it for its own purposes).
     
    Tautvydas-Zilys, Sep 20, 2021
    #11

  12. DrewFitz

    DrewFitz

    Joined:
    Dec 9, 2016
    Posts:
    30
    Fascinating, I’d love to know how you tracked that down, sounds like a tricky bug!
     
    DrewFitz, Sep 20, 2021
    #12

  13. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,423
    Figuring out how to fix it was harder than figuring out what was going on :). Attaching a debugger was enough for it to tell me that we were crashing when trying to use the value read from that register.
     
    Tautvydas-Zilys, Sep 20, 2021
    #13

  14. alex_bussman

    alex_bussman

    Joined:
    Aug 15, 2013
    Posts:
    5
    It also seems like this issue is gone with macOS 12 beta 7
     
    alex_bussman, Sep 22, 2021
    #14

  15. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,423
    Looks like we weren't the only ones fixing stuff then :).
     
    Tautvydas-Zilys, Sep 22, 2021
    #15
    alex_bussman likes this.