Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0b6
Issue ID
1004878
Regression
No
Unity crashes at RaycastCommandJob when going from 30000 to 40000 batched raycasts per frame
To reproduce:
1. Make sure you have installed Unity that supports experimental ECS and C# jobs system
2. Open user's attached project
3. Open "BatchedRaycasts" scene
4. Enter play mode
5. Hit "Toogle Test Mode" button few times (till Unity crashes)
Expected result: Cycling between a different number of batched raycasts shouldn't crash the Editor.
Actual result: Editor crashes when going from 30000 to 40000 of batched raycasts.
Reproduced with:
Version 2018.1.0b6 (89b72894c1ef)
Sat, 10 Feb 2018 21:45:46 GMT
Branch: 2018.1/scripting/jobsystem/playground
Fixed in: Unity 2018.2.0a4
Backported to: 2018.1.0b11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Create Node Menu is not closing and “NullReferenceException: Object reference not set to an instance of an object” error is thrown when Shader Graph window is closed
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
Add comment