Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0b10
Issue ID
1072951
Regression
Yes
Crash in CalculateSurfaceArea after opening the project with certain mesh
Steps to repro:
1. Open attached project.
Expected result:
Project opens without crashes.
Actual result:
Editor crashes.
Regression introduced in Unity 2018.2.0b10.
Last calls from the stacktrace:
0x0000000140843914 (Unity) CalculateSurfaceArea
0x0000000140843325 (Unity) CalculateNormalizedLightmapArea
0x0000000140833D39 (Unity) MeshRenderer::GetCachedNormalizedLightmapArea
0x0000000141147FA5 (Unity) AddInstance
0x000000014114EA78 (Unity) ExtractGIInstances
0x0000000141162911 (Unity) GISceneManager::GetGeometries
Notes:
- Reproducible in 2018.2.5f1, 2018.2.0b10;
- Not reproducible in 2018.3.0a9, 2018.2.0b9, 2018.1.9f1, 2017.4.9f1, 2017.2.3p3;
- Reproducible on Windows and OSX;
- Opening the project in 2018.3.0b9 and earlier fixes the issue;
- In the latest 2018.3 reference to the prefab that's causing the bug is broken, so the bug might be masked out in this version.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Add comment