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. Dismiss Notice

Unity editor hangs on start up

Discussion in 'Editor & General Support' started by daisySa, Jan 22, 2016.

  1. daisySa

    daisySa

    Joined:
    Dec 29, 2011
    Posts:
    341
    I’m unable to start the Unity editor - it just hangs. This happens in OS X and Windows 8.1, on Unity 5.2.2, 5.2.4 and 5.3.1p3.

    On OS X I’m getting this message in the editor log:

    Native extension for OSXStandalone target not found


    The workaround is to delete /Library and restart, but the rebuild takes around 5 hours each time as the project is 110GB. This is now happening every day, making working in Unity very difficult.

    I opened a case (759598) a couple of weeks ago but I still haven't heard back from Unity support.

    Any ideas from anyone?
     
  2. daisySa

    daisySa

    Joined:
    Dec 29, 2011
    Posts:
    341
    To add to this, I also tried just deleting /ScriptAssemblies to force a recompilation without reimporting all the assets, but it didn’t help.

    Also, there are no obvious errors in the shader compiler log.
     
  3. daisySa

    daisySa

    Joined:
    Dec 29, 2011
    Posts:
    341
    Some more information:
    • Software: Unity 5.3.1p3, OS X El Capitan 10.11.2
    • Hardware: iMac Retina 5K 27", 4.0 GHz i7, 32GB, 3TB (128GB SSD), AMD Radeon R9 M395X (4GB VRAM)
     
  4. daisySa

    daisySa

    Joined:
    Dec 29, 2011
    Posts:
    341
    It's just happened again (as it does every morning), and all I did was select a new window layout while compilation was in progress. Looks like I'll be doing something else for the next 5 hours. :(

    A response from Unity would be nice. No-one else is seeing this issue on OS X since 5.2.x?
     
  5. mhannum72

    mhannum72

    Joined:
    Jul 23, 2017
    Posts:
    3
    In my case it was hung on a semaphore- if you kill Unity while it's starting up, the semaphore can be left in a "bad state". The fix is to reboot your machine.