Search Issue Tracker
By Design
Votes
0
Found in
2022.3.2f1
2023.1.0f1
2023.2.0a18
Issue ID
UUM-39959
Regression
No
Custom editors are recreated when assigning a material to a GameObject
Reproduction steps:
1. Open project “Bug Test 2.zip”
2. Open scene “Test”
3. Select “Cube” GameObject in the Hierarchy
Expected result: only one “Hello i am a new editor” message is printed in the Console
Actual result: “Hello i am a new editor” messages are flooded in the Console - when a custom editor assigns a material to an object it is constantly remade
Reproducible with: 2022.3.2f1, 2023.1.0f1, 2023.2.0a18
Couldn’t test with: 2021.3.27f1 (due to compiler errors)
Reproducible on: macOS Ventura 13.2.1 (Intel), Windows 10 (by the reporter)
Note: Commenting out line 18 in “NewBehaviourScript.cs” gives expected results
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
- 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
- Errors and warnings are thrown after installing Visual Effect Graph Learning Samples
Resolution Note:
Editors are currently recreated when the inspected object is marked as dirty. Changing the material of an object will cause the object to dirty itself and may trigger the construction of a new editor.
Unity will recycle the editors to some extent, but there's no guarantee that the same instance will be used for a particular object.