Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a13
2019.2.0b6
Issue ID
1163914
Regression
Yes
Creating a Prefab with a script containing a NameToLayer from MonoBehaviour constructor freezes/crashes the Editor
How to reproduce:
1. Create a new Unity project
2. Import the tester-attached script(Bug.cs)
3. Create a new GameObject and attach the script
4. Create a Prefab from this GameObject
5. If the Editor does not freeze/crash at this point - create more Prefabs from separate GameObjects with this script
Expected result: the Editor does not crash/become unresponsive
Actual result: the Editor crashes/becomes unresponsive
Reproducible with: 2019.1.0a13, 2019.1.8f1, 2019.2.0b7, 2019.3.0a7
Not reproducible with: 2017.4.29f1, 2018.4.3f1, 2019.1.0a12
Notes:
The Editor crashes without freezing or any stack trace on Windows
The Editor freezes on macOS, crashes when closed with 2019.3 versions of Unity
With 2019.1.0a11 and 2019.1.0a12, creating a Prefab from a GameObject with the script does not freeze, but sometimes crashes the Editor
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