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

Editor Crash + Scene delete

Discussion in 'Editor & General Support' started by Smileys, Jan 15, 2015.

  1. Smileys

    Smileys

    Joined:
    Feb 27, 2014
    Posts:
    81
    Hi,
    im using Unity 4.6.1 Pro on a MacBook Pro late 2013 with 8GB ram + i5.
    Unity crashes about every 20 minutes when im working on my main Scene.

    EDIT: Ive just confirmed that this is not because of "working" in Unity.
    I had unity open on a fresh start and left the Mac. 30 min later Unity was "dead" with the console window flooded ( "UNSUPPORTED").

    All meshes in editor window turn to a rainbow like color - then Unity crashes.
    Worst of all - the Scene gets deleted every time. Its not in "temp" or anywhere on my Mac.
    Unity seems to just "save delete" it. This makes working on my Game nearly impossible.
    Im Backing up Scenes like crazy. Is there any fix for that behavior or is it a known bug?
    Right now im really angry about this behavior on a software that expensive.
    In addition to that i constantly get out of memory crashes on really easy tasks and unitys just using about 600-800mb of ram.
    I cant even tell you if it is since the 4.6 update because a lot changes every day. But it is definitely worse since the update.

    Some data:
    Scene size - 18mb
    Terrain:
    width 2000
    length 2000
    height 600
    height res 2049
    Detail res 2048
    Detail res per patch 16
    control tex res 2048
    base tex res 2048

    Most scene objects (Rocks) have convex mesh collider.
    Trees have capsule collider and 2 LODs.
     
    Last edited: Jan 15, 2015
  2. Graham-Dunnett

    Graham-Dunnett

    Unity Technologies

    Joined:
    Jun 2, 2009
    Posts:
    4,287
    Can you post the Editor.log after Unity crashes next time. It might help explain what's happening.
     
  3. Smileys

    Smileys

    Joined:
    Feb 27, 2014
    Posts:
    81
    Log as txt file.
    Found this thread - this pretty much describes my problem.
    But the out of memory issue is has nothing to do with this.
    EDIT: Just noticed that my Scene was not deleted on this crash. thats the first time.
     

    Attached Files:

  4. Graham-Dunnett

    Graham-Dunnett

    Unity Technologies

    Joined:
    Jun 2, 2009
    Posts:
    4,287
    That looks like Unity has run out of memory and is trying to display an error window. Displaying that window has caused some OSX code to fall over. If that's got nothing to do with your crash, and the crash this time was different, maybe wait until you see a more familiar crash, and post that log.
     
  5. Smileys

    Smileys

    Joined:
    Feb 27, 2014
    Posts:
    81
    No - this is my main problem. It is exactly what happens every 20 minutes.
    The other out of memory issues appear randomly on texture imports, mesh changes etc. For example i import a 1024 texture (png) and unity crashes. Then i restart it and import again and everything is just fine. I can pretty much live with that behavior. But not with unity crashing every 20 mins + trashing my scenes.
     
  6. Smileys

    Smileys

    Joined:
    Feb 27, 2014
    Posts:
    81
    Just updated Yosemite and started Unity - next crash.
     

    Attached Files:

  7. Smileys

    Smileys

    Joined:
    Feb 27, 2014
    Posts:
    81
    Next crash - 19 mins.
    No work in unity done - i was just writing in monodev.
     

    Attached Files:

  8. Fritsl

    Fritsl

    Joined:
    Mar 10, 2013
    Posts:
    211
    Unity crashes my Mac like this yes, also about every 20 minutes.

    Sometimes I am not even at the computer, I am like opening the door for someone, and I sit down again and Unity is crashed. I have tried to just sit and read the screen with no touch of mouse or keyboard and suddently Unity crashes.

    I get all the UNSUPPORTED crashes, I get all the out of momory crashes, I get those that opens the bug report window, and thoses that do not.

    I am trying to tell Unity Tech that there is a major issue here, and I'm told to write in the forums, where each time I'm told that 'this is another case'..

    Graham - here you see yet another tread like these - as I understand on in the other tread where you argued, there are no issues on Unity / Mac? Please, look sir, I am NOT the only one. Yes, I AM aware that there are many Ma'cs running Unity, and that apparently according to you most of them without issues. But then there are the rest of us, and it's NOT just isolated instances, we see a complete freak show of crashes all the time.

    I have now submitted at least 30 bug repports, how long should this go on before you realize there is an actual isue, and you cannot just say 'this is a OSX Open GL, and this is that and this is that - overall there is a profound bug, and you need to address this.

    I am trying hard to give all details on every crash - but how would you submit a bug report in details when for the 6th time before the morning coffee Unity crashed just when you pressed Play? How many details can be given? It crashes constantly!! Skærmbillede 2015-01-27 kl. 12.59.11.png Skærmbillede 2015-01-22 kl. 12.57.20.png
     
  9. Pr3s4ri0

    Pr3s4ri0

    Joined:
    Mar 5, 2013
    Posts:
    11
    I don't know if this is related or not but on the lates Unity 4.6.1p5 (OSX 10.9.5 13F34 MBP Intel Core i7 2,6 GHz 16 GB 1024 MB MacStandaloneSupport) Editor crashes every time it has to recompile c# scripts if was in play mode before script modification.

    So reproduction is:
    1) Start unity and open scene with attached c# script
    2) play in editor and then stop
    3) edit your script and save
    4) wait for unity to recompile
    5) UNITY CRASHES

    Editio.Log
    Reloading assemblies after finishing script compilation.
    Begin MonoManager ReloadAssembly
    Receiving unhandled NULL exception
    Launching bug reporter
    Obtained 22 stack frames.
    #0 0x0000000448855a in mono_class_array_element_size
    #1 0x0000000072d462 in scripting_array_new(MonoClass*, unsigned long, unsigned long)
    #2 0x0000000086df40 in TryVerifySignature(char const*, unsigned char const*)
    #3 0x0000000086dd70 in FindAndLoadUnityPlugin(char const*)
    #4 0x000000044b962e in mono_lookup_pinvoke_call
    #5 0x000000044cd22e in mono_marshal_get_native_wrapper
    #6 0x000000043d9803 in mono_method_to_ir
    #7 0x000000043ba0b6 in mini_method_compile
    #8 0x000000043bbdb3 in mono_jit_compile_method
    #9 0x000000043bb77f in mono_jit_compile_method
    #10 0x000000044f313c in mono_compile_method
    #11 0x00000004439872 in mono_magic_trampoline
    #12 0x00000005f68066 in (Unknown)
    #13 0x00000010720512 in (wrapper runtime-invoke) object:runtime_invoke_virtual_void__this__ (object,intptr,intptr,intptr) + 0x92 (0x10720480 0x107205dd) [0x6f48a80 - Unity Child Domain]
    #14 0x000000044a153c in mono_gc_run_finalize
    #15 0x000000044a2ec1 in mono_gc_init
    #16 0x0000000451f929 in mono_thread_create_internal
    #17 0x00000004553334 in CreateThread
    #18 0x000000045792b1 in GC_start_routine
    #19 0x00000098c615fb in _pthread_body
    #20 0x00000098c61485 in _pthread_struct_init
    #21 0x00000098c66cf2 in thread_start

    *** Launching bug reporter due to crashbug.
    Obtained 27 stack frames.
    0 Unity 0x016a6c61 _Z17LaunchBugReporter13BugReportMode + 1073
    1 Unity 0x0095fb25 _Z12HandleSignaliP9__siginfoPv + 53
    2 libmono.0.dylib 0x0447185e mono_chain_signal + 76
    3 libmono.0.dylib 0x043bc926 mono_sigsegv_signal_handler + 234
    4 libsystem_platform.dylib 0x983a5deb _sigtramp + 43
    5 ??? 0xffffffff 0x0 + 4294967295
    6 Unity 0x0072d462 _Z19scripting_array_newP9MonoClassmm + 18
    7 Unity 0x0086df40 _ZL18TryVerifySignaturePKcPKh + 128
    8 Unity 0x0086dd70 _Z22FindAndLoadUnityPluginPKc + 64
    9 libmono.0.dylib 0x044b962e mono_lookup_pinvoke_call + 586
    10 libmono.0.dylib 0x044cd22e mono_marshal_get_native_wrapper + 390
    11 libmono.0.dylib 0x043d9803 mono_method_to_ir + 95999
    12 libmono.0.dylib 0x043ba0b6 mini_method_compile + 2252
    13 libmono.0.dylib 0x043bbdb3 mono_jit_compile_method + 1637
    14 libmono.0.dylib 0x043bb77f mono_jit_compile_method + 49
    15 libmono.0.dylib 0x044f313c mono_compile_method + 36
    16 libmono.0.dylib 0x04439872 mono_magic_trampoline + 2184
    17 ??? 0x05f68066 0x0 + 100040806
    18 ??? 0x10720512 0x0 + 275907858
    19 libmono.0.dylib 0x044a153c mono_gc_run_finalize + 1020
    20 libmono.0.dylib 0x044a2ec1 mono_gc_init + 1135
    21 libmono.0.dylib 0x0451f929 mono_thread_create_internal + 1645
    22 libmono.0.dylib 0x04553334 CreateThread + 1558
    23 libmono.0.dylib 0x045792b1 GC_start_routine + 108
    24 libsystem_pthread.dylib 0x98c615fb _pthread_body + 144
    25 libsystem_pthread.dylib 0x98c61485 _pthread_struct_init + 0
    26 libsystem_pthread.dylib 0x98c66cf2 thread_start + 34

    I have submited bug report 667910

    Update: This issue seems to be already resolved in 4.6.2f1
     
    Last edited: Jan 29, 2015