Been getting this every now and again for the past time. Anyone know what it means and how it can be fixed?
No more information is specified when clicking the message.
This information can be found when checking the editor log file:
results->dynamicBounds.empty()
(Filename: C:/buildslave/unity/build/Runtime/Camera/ShadowCulling.cpp Line: 617)
Same error here. Sometimes Unity crashes after that.
Weβre also experiencing this with no crash log in the editor with version 5.2.3f1.
Iβm having the same error here! Unity crashes instantly with the error log: results->dynamicBounds.empty()
Looks like the error appears randomly after the game is running sometimes after 20 minutes sometimes after 5 minutes⦠Happens also in a standalone build.
Iβm using Unity 5.2 maybe this is a known bug?
results->dynamicBounds.empty()
(Filename: C:/buildslave/unity/build/Runtime/Camera/ShadowCulling.cpp Line: 616)
Crash!!!
I am also having the same issue. If anyone has a solution I can try, please let me know. Unity crashing after a few minutes of runtime is destroying my productivity. It doesnβt seem to be tied to anything in particular that I do other than the editor is currently in play mode. I can start play mode and walk away, when i come back 5 min later iβll be looking at a crash submit form. Other times I will be actively debugging an animation and poof, the same error.
Unity.exe caused an Access Violation (0xc0000005)
in module Unity.exe at 0033:400de986.
Error occurred at 2016-01-06_173018.
C:\Program Files\Unity\Editor\Unity.exe, run by Dumoose.
57% memory in use.
4095 MB physical memory [1728 MB free].
8188 MB paging file [4458 MB free].
8388608 MB user address space [8386456 MB free].
Read from location 00000380 caused an access violation.
results->dynamicBounds.empty()
(Filename: C:/buildslave/unity/build/Runtime/Camera/ShadowCulling.cpp Line: 599)
Crash!!!
Some kind of Unity core error. We have to wait for Unity to fix it. File crash reports, all of you please!
This is no longer a problem for us in 5.3.1p1 (canβt speak for 5.3.1 because we skipped it).
Hi! Still trying to find out what the reason of this errorβ¦
Same error log:
Unity.exe caused an Access Violation (0xc0000005) in module Unity.exe
Log from unity editor: results->dynamicBounds.empty()
After this message shows (results->dynamicBounds.empty()), Unity crashes 1-2 seconds after that.
Tested on versions: 5.1.1f1, 5.2.2f1, 5.2.4f1,5.3.0f4,5.3.1f1 and latest 5.3.1p3.
Game is 3D action, so itβs using terrain, unity trees, physics etc.
What can be reason of this error? What should i do to avoid it? 3 weeks spent to find out whatβs the reason. 
It happens randomly from 2 to 15 minutes in editor and it seems to be a reason of crashes on mobile devices. Does anybody know something about it?
Soooooo did anyone file a bug report?
Maybe UI received a directional light, should not Use directional light to illuminate UI.Because some are too small and the direction of the problem leads to a shadow of 0.
is this bug still alive in the latest Unity 5.3.4? I really hope Unity fixed it.
I didnβt updated my project so I canβt test with the latest Unity version and i canβt reproduce it in an empty project.
unfortunately this bug is still existent in Unity 5.3.4
@karl_jones I have submitted a bug report: Case 783827
So Iβve played with the latest Unity 5.3.4, and as soon as the Build crashes thereβs a Message coming up, something like: Oops the game has crashed, the funny thing is that, as long as I donβt click OK on the popup the game still runs fine without crash, and I can play it normally. While in Unity 5.2.X it crashes immediately.
Stack trace Output.log:
0x01362B5C (Game) [c:\buildslave\unity\build\runtime\camera\shadowculling.cpp:602] GenerateCombinedDynamicVisibleListJob
0x013C4B7B (Game) [c:\buildslave\unity\build\runtime\jobs\internal\jobqueue.cpp:345] JobQueue::Exec
0x013C4CE1 (Game) [c:\buildslave\unity\build\runtime\jobs\internal\jobqueue.cpp:717] JobQueue::ProcessJobs
0x015640ED (Game) [c:\buildslave\unity\build\runtime\threads\thread.cpp:40] Thread::RunThreadWrapper
0x7674338A (kernel32) BaseThreadInitThunk
0x77259A02 (ntdll) RtlInitializeExceptionChain
and from the error.log:
Game.exe caused an Access Violation (0xc0000005)
in module Game.exe at 0023:01362b5c.
Error occurred at 2016-03-30_190454.
62% memory in use.
0 MB physical memory [0 MB free].
0 MB paging file [0 MB free].
0 MB user address space [1768 MB free].
Read from location 00000340 caused an access violation.
Context:
EDI: 0x15ed6c70 ESI: 0x165705d0 EAX: 0x000002f0
EBX: 0x03ab36ac ECX: 0x00000000 EDX: 0x0043f5cc
EIP: 0x01362b5c EBP: 0x087df888 SegCs: 0x00000023
EFlags: 0x00010202 ESP: 0x087df87c SegSs: 0x0000002b
Bytes at CS:EIP:
8b 81 40 03 00 00 e8 f9 fd ff ff 83 c4 0c 5d c3
Hi guys, I had the same problem (Editor crash and βForced Closeβ for mobile devices). I am using NGUI for my game. The problem seems to be solved by moving all NGUI GameObjects into βUIβ Layer and turning off βUIβ layer from my lightβs culling mask.
Hope this works for you tooβ¦
@bardia68 Ok I guess I owe you a beer! 
Iβm still testing it (Unity 5.2.4), but as for now it looks pretty good and I think that actually fixed the bug!
Some more details:
ΜΆsΜΆΜΆoΜΆΜΆ ΜΆΜΆsΜΆΜΆoΜΆΜΆmΜΆΜΆeΜΆΜΆtΜΆΜΆhΜΆΜΆiΜΆΜΆnΜΆΜΆgΜΆΜΆ ΜΆΜΆwΜΆΜΆeΜΆΜΆiΜΆΜΆrΜΆΜΆdΜΆΜΆ ΜΆΜΆiΜΆΜΆsΜΆΜΆ ΜΆΜΆhΜΆΜΆaΜΆΜΆpΜΆΜΆpΜΆΜΆeΜΆΜΆnΜΆΜΆiΜΆΜΆnΜΆΜΆgΜΆΜΆ ΜΆΜΆwΜΆΜΆiΜΆΜΆtΜΆΜΆhΜΆΜΆ ΜΆΜΆtΜΆΜΆhΜΆΜΆeΜΆΜΆ ΜΆΜΆsΜΆΜΆhΜΆΜΆaΜΆΜΆdΜΆΜΆoΜΆΜΆwΜΆΜΆsΜΆΜΆ ΜΆΜΆiΜΆΜΆnΜΆΜΆ ΜΆΜΆcΜΆΜΆoΜΆΜΆmΜΆΜΆbΜΆΜΆiΜΆΜΆnΜΆΜΆaΜΆΜΆtΜΆΜΆiΜΆΜΆoΜΆΜΆnΜΆΜΆ ΜΆΜΆwΜΆΜΆiΜΆΜΆtΜΆΜΆhΜΆΜΆ ΜΆΜΆtΜΆΜΆhΜΆΜΆeΜΆΜΆ ΜΆΜΆuΜΆΜΆiΜΆΜΆ.ΜΆΜΆ ΜΆΜΆiΜΆΜΆ ΜΆΜΆdΜΆΜΆoΜΆΜΆ ΜΆΜΆnΜΆΜΆoΜΆΜΆtΜΆΜΆ ΜΆΜΆuΜΆΜΆsΜΆΜΆeΜΆΜΆ ΜΆΜΆaΜΆΜΆnΜΆΜΆyΜΆΜΆ ΜΆΜΆfΜΆΜΆaΜΆΜΆnΜΆΜΆcΜΆΜΆyΜΆΜΆ ΜΆΜΆuΜΆΜΆiΜΆΜΆ ΜΆΜΆsΜΆΜΆhΜΆΜΆaΜΆΜΆdΜΆΜΆeΜΆΜΆrΜΆΜΆsΜΆΜΆ,ΜΆΜΆ ΜΆΜΆjΜΆΜΆuΜΆΜΆsΜΆΜΆtΜΆΜΆ ΜΆΜΆtΜΆΜΆhΜΆΜΆeΜΆΜΆ ΜΆΜΆdΜΆΜΆeΜΆΜΆfΜΆΜΆaΜΆΜΆuΜΆΜΆlΜΆΜΆtΜΆΜΆ ΜΆΜΆoΜΆΜΆnΜΆΜΆeΜΆΜΆsΜΆΜΆ.ΜΆΜΆ ΜΆΜΆiΜΆΜΆ ΜΆΜΆhΜΆΜΆaΜΆΜΆvΜΆΜΆeΜΆΜΆ ΜΆΜΆtΜΆΜΆwΜΆΜΆoΜΆΜΆ ΜΆΜΆcΜΆΜΆaΜΆΜΆnΜΆΜΆvΜΆΜΆaΜΆΜΆsΜΆΜΆeΜΆΜΆsΜΆΜΆ ΜΆΜΆbΜΆΜΆoΜΆΜΆtΜΆΜΆhΜΆΜΆ ΜΆΜΆrΜΆΜΆeΜΆΜΆnΜΆΜΆdΜΆΜΆeΜΆΜΆrΜΆΜΆiΜΆΜΆnΜΆΜΆgΜΆΜΆ ΜΆΜΆiΜΆΜΆnΜΆΜΆ ΜΆΜΆsΜΆΜΆcΜΆΜΆrΜΆΜΆeΜΆΜΆeΜΆΜΆnΜΆΜΆ ΜΆΜΆsΜΆΜΆpΜΆΜΆaΜΆΜΆcΜΆΜΆeΜΆΜΆ ΜΆ-ΜΆ ΜΆΜΆoΜΆΜΆvΜΆΜΆeΜΆΜΆrΜΆΜΆlΜΆΜΆaΜΆΜΆyΜΆΜΆ.ΜΆ
edit: itβs still crashingβ¦
sigh looks like I was happy to early, had some more time again to test, and it is still crashing!
Iβm getting this error as well. It crashes every time I run the game, sometimes after a few seconds, sometimes after a few minutes. Iβm sure itβs related to Static Lightmap baking, because I did that for the first time today, and even after clearing the baked data the problem persists.
I tried searching for this case in the Issue Tracker, but nothing came up for this number. Do you know if it was dealt with? Or have you managed to find a fix? The only thing that seems to fix it is turning of shadows from the directional light. Thanks.
@jonfinlay No, Unity didnβt fixed anything related to this bug. Iβm currently trying to make a new project where this bug can be reproduced for Unity but as for now I had no luck and also no time.
Hereβs the bug report: https://fogbugz.unity3d.com/default.asp?783827_rupm1p1sihrt8acv
I didnβt tried it with static lightmap baking, will have a look at it.
Please fill out a bug report too, you can refer to this thread and to the bug report Case: 783827
If you have a project where Unity can reproduce this bug then upload it as well.
@jonfinlay have you got any success reproducing the bug?
I just got an email from Unity you can read it in the bug report
https://fogbugz.unity3d.com/default.asp?783827_rupm1p1sihrt8acv
Iβm still trying to create a repro project but as for now it just wonβt crashβ¦ Unfortunately it is also very time consuming and I canβt sacrifice more time for it.
One interesting thing is, that in my case if I create a new scene inside of my crashing project and i add the same light with shadows and build it, it does not crash. β So I assume there must be something very specific in the other scene which causes the crash and it is not project dependent.
So next thing I wanβt to try is to test it with additive scene loading, asset bundle loading, skinned meshesβ¦