Search Unity

Unity 5.6.2p4 - 2017.1of3 - 2017.20b4 Crash on Mac at open

Discussion in 'Editor & General Support' started by hacaro76, Jul 24, 2017.

  1. hacaro76

    hacaro76

    Joined:
    Oct 14, 2015
    Posts:
    25
    Dear all, I've installed the Unity 5.6.2p4 to try to solve a problem of memory leak on my mac.

    Unfortunately, i've noticed that Unity 5.6.2p4 crash at startup. It happens also with a Clean New project.

    My configuration is :
    MacBook Pro (Retina, 15-inch, Mid 2014)
    Mac Os Sierra 10.12.6 (16G29) updated today ** but also crash on previous version of sierra.

    Here the complete error : http://sensasenso.com/Unity_5.6.2p4_crash_report_mac.txt

    Anyone can help ?

    [UPDATE] it happens also at 2017.10f3 and 2017.20b4.

    It's rally strange, at the moment i can work only on 5.6.2f1 !! please someone can help me ?


    Thanks in advance and best regards.
     
    Last edited: Jul 25, 2017
  2. hacaro76

    hacaro76

    Joined:
    Oct 14, 2015
    Posts:
    25
    No one that have the same situation ?
     
  3. yigitdream

    yigitdream

    Joined:
    May 8, 2017
    Posts:
    2
    yes ı have. After the OS X 10.12.6 update all the versions give an error when unity unfocused in play mode. (5.6.1.p1 ,5.6.2p4 ,2017.1.0p1 )
     
  4. yigitdream

    yigitdream

    Joined:
    May 8, 2017
    Posts:
    2
     
  5. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,300
    Can you file a bug report please?
     
  6. hacaro76

    hacaro76

    Joined:
    Oct 14, 2015
    Posts:
    25
  7. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,300
  8. dougj99

    dougj99

    Joined:
    Nov 4, 2017
    Posts:
    2
    Hello Karl,

    Was this issue ever resolved? I'm having the exact same problem and I'm completely dead in the water....

    Thanks!
     
  9. karl_jones

    karl_jones

    Unity Technologies

    Joined:
    May 5, 2015
    Posts:
    8,300
    I dont know. I would need the bug number to check. hascaro76 never posted it. Have you filed a bug report?