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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment