Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

Light Probes crash Web Player often.

Discussion in 'Unity 5 Pre-order Beta' started by AustinRichards, Jan 11, 2015.

  1. AustinRichards

    AustinRichards

    Joined:
    Apr 4, 2013
    Posts:
    321
    Found a bug for you guys.
    Whenever I bake light probes It tends to crash unity webplayer. It runs perfectly in editor & standalone.

    Here's the error code from the web player log. Something to do with releasing the active render texture.

    Code (CSharp):
    1. 002066BA (chrome) IsSandboxedProcess
    2. 74FB2764 (KERNEL32) BaseThreadInitThunk
    3. 7771DC7A (ntdll) RtlFreeSid
    4. 7771DC45 (ntdll) RtlFreeSid
    5.  
    6. ========== END OF STACKTRACE ===========
    7.  
    8. 150110 22:39:22 Setting error display: 'The content was stopped because a fatal
    9. content error has been detected.', details: '', link: 0
    10. web: shutdown player
    11. Releasing render texture that is set to be RenderTexture.active!
    12. (Filename: C:/buildslave/unity/build/Runtime/Graphics/RenderTexture.cpp Line: 452)
    13.  
    14. RenderTexture warning: Destroying active render texture. Switching to main context.
    15. (Filename: C:/buildslave/unity/build/Runtime/GfxDevice/d3d11/RenderTextureD3D11.cpp Line: 815)
    16.  
    17. web: shutdown finished
    18. 150110 22:39:22 loader: final cleanup
    19. 150110 22:39:22 loader: unload unity dll
    Using chrome (unsure about other browsers), Unity 5 beta 18.
    I can upload one upon request though if you guys can't reproduce it... But this happens with any scene for me.
     
  2. KEngelstoft

    KEngelstoft

    Unity Technologies

    Joined:
    Aug 13, 2013
    Posts:
    1,366
    Hi! What is the case number for this one?
     
  3. AustinRichards

    AustinRichards

    Joined:
    Apr 4, 2013
    Posts:
    321
    Case 662804
     
  4. Kuba

    Kuba

    Moderator

    Joined:
    Jan 13, 2009
    Posts:
    416
    The bug was verified by QA yesterday and we'll get to it, worry not. :)