Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice

5.3.4p2 OS X Editor crashing

Discussion in 'macOS' started by Nabren, Apr 11, 2016.

  1. Nabren

    Nabren

    Joined:
    Mar 7, 2014
    Posts:
    61
    I am receiving a lot of editor crashes using the 5.3.4p2 OS X Editor (does not crash in the same way in 5.3.4p1). I haven't been able to reproduce this in a smaller project unfortunately to submit a bug report. Has anyone seen a similar stack trace and have any ideas?

    Receiving unhandled NULL exception
    Launching bug reporter
    Obtained 24 stack frames.
    #0 0x007fff89115a3f in OSAtomicAdd64Barrier$VARIANT$mp
    #1 0x00000100df6655 in MemoryManager::RegisterDeallocation(void*, MemLabelId const&, char const*)
    #2 0x00000100df4752 in MemoryManager::Deallocate(void*, MemLabelId const&)
    #3 0x000001012bbe79 in UTF16String::~UTF16String()
    #4 0x0000010220df7a in TextRenderingPrivate::TextMeshGenerator::GarbageCollect()
    #5 0x000001019f52b8 in Application::UpdateScene(bool)
    #6 0x000001019f2629 in Application::UpdateSceneIfNeeded()
    #7 0x000001019f1cb7 in Application::TickTimer()
    #8 0x007fff8f303d6c in __NSFireTimer
    #9 0x007fff8c40db94 in __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__
    #10 0x007fff8c40d823 in __CFRunLoopDoTimer
    #11 0x007fff8c40d37a in __CFRunLoopDoTimers
    #12 0x007fff8c404871 in __CFRunLoopRun
    #13 0x007fff8c403ed8 in CFRunLoopRunSpecific
    #14 0x007fff938f7935 in RunCurrentEventLoopInMode
    #15 0x007fff938f776f in ReceiveNextEventCommon
    #16 0x007fff938f75af in _BlockUntilNextEventMatchingListInModeWithFilter
    #17 0x007fff87718efa in _DPSNextEvent
    #18 0x007fff8771832a in -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
    #19 0x007fff8770ce84 in -[NSApplication run]
    #20 0x007fff876d646c in NSApplicationMain
    #21 0x00000101c55f48 in EditorMain(int, char const**)
    #22 0x00000101c565f9 in main
    #23 0x000001000020c4 in start
     
  2. scritchy

    scritchy

    Joined:
    Dec 30, 2010
    Posts:
    94
    Yup, same problem. not exactly the same stack but pretty similar, ending in a memorymanager crash.
    i had to go back to p1. filing a bug.
     
    Nabren and MrEsquire like this.