Search Unity

5.2f3 : weird crash/error logs when changing scenes from a specific scene

Discussion in '5.2 Beta' started by raziel_anarki, Sep 9, 2015.

  1. raziel_anarki

    raziel_anarki

    Joined:
    Jun 1, 2014
    Posts:
    58
    I have a scene (lets call it "c1") in my project, which when loaded, has no problems, and runs fine insdie/outside the editor.

    however when
    a- i click "file/new scene" the editor crashes, and bombs out to the error reporting screen
    b- i load another scene from the project view: the new scene gets loaded, and i get a bunch of "Failed to issue albedo update." messages. after that i can "new scene" all i want, until i load the "c1" scene again.

    here's a copy of the stack trace from the end of the crash log
    Code (csharp):
    1.  
    2. 0x00000001400D584F (Unity) LightProbes::GetPendingCoefficientsOffset
    3. 0x00000001413BB430 (Unity) EnlightenRuntimeManager::AllocateAndEnqueProbeSet
    4. 0x00000001413BEF3C (Unity) EnlightenRuntimeManager::IssueProbeSetUpdates
    5. 0x00000001413BF533 (Unity) EnlightenRuntimeManager::RepairProbeSetState
    6. 0x00000001413BF8CF (Unity) EnlightenRuntimeManager::UpdateFromDataManager
    7. 0x00000001413BFE8B (Unity) EnlightenRuntimeManager::Prepare
    8. 0x00000001413BFF76 (Unity) EnlightenRuntimeManager::Update
    9. 0x00000001408AF6DC (Unity) gi::PostUpdate
    10. 0x00000001408AC9B2 (Unity) GISceneManager::Update
    11. 0x00000001408ACD07 (Unity) std::_Sort<std::pair<int,Hash128> * __ptr64,__int64,vector_map<int,Hash128,std::less<int>,stl_allocator<std::pair<int,Hash128>,72,16> >::value_compare>
    12. 0x000000014014C542 (Unity) CallbackArray::Invoke
    13. 0x0000000140C77091 (Unity) Application::TickTimer
    14. 0x0000000140E35FA4 (Unity) RelaunchUnity
    15. 0x0000000140E3759B (Unity) WinMain
    16. 0x000000014152EC80 (Unity) strerror_s
    17. 0x0000000076FB5A4D (kernel32) BaseThreadInitThunk
    18. 0x00000000770EB831 (ntdll) RtlUserThreadStart
    19.  

    i hope someone has an idea as to what could be the culprit,
    or what i might be doing wrong, and where should i look for solutions.

    the project is rather large, and i cannot seem to isolate and reproduce the problem on it's own, but if need be, i could try to submit the whole thing using the crash reporter.
     
  2. KEngelstoft

    KEngelstoft

    Unity Technologies

    Joined:
    Aug 13, 2013
    Posts:
    1,134
    Hi! Do you have the frame debugger open? Can you please attach the entire editor.log?
     
  3. raziel_anarki

    raziel_anarki

    Joined:
    Jun 1, 2014
    Posts:
    58
    no, frame debugger was not open, just some standard windows, and a custom editor window for the project.

    i've attached the editor.log as a zip:
     

    Attached Files:

    Last edited: Sep 10, 2015
unityunity