Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.0b5
2018.1.0b7
Issue ID
1001287
Regression
Yes
Application crash when enabling renderer
Steps to reproduce:
1) Download attached project and open in Unity
2) Enter play mode in "_Complete-Game" scene
3) Wait until the enemy will be close to you
4) Start shooting in his direction
Note: editor should crash
5) If 1st enemy died and application did not crash, restart and repeat 3-5 steps
Reproduced with:
2018.1.0b5, 2018.1.0b7
Not reproduced with:
2017.2.1p4, 2017.3.1p1, 2018.1.0b4
Regression since:
2018.1.0b5
Devices under testing:
0154 || Samsung Galaxy Note 8, OS: 7.1.1, CPU: Samsung Exynos 9 Octa, GPU: Mali-G71
0150 || Google Pixel XL, OS: 8.0, CPU: Snapdragon 821, GPU: Adreno 530
0162 || Razer Phone, OS: 7.1.1, CPU: Qualqomm Snapdragon 835, GPU: Adreno 540
0131 || Huawei P9, OS: 7.0, CPU: HiSilicon Kirin 955, GPU: Mali-T880
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #999559