Search Issue Tracker
Fixed
Fixed in 6000.0.18f1, 6000.1.0a1, 7000.0.0a1
Votes
4
Found in
2021.3.39f1
2022.3.33f1
6000.0.7f1
6000.1.0a7
7000.0.0a1
Issue ID
UUM-74316
Regression
No
VisualElements that use TrackPropertyValue keep tracking properties when they are removed
Reproduction steps:
1. Open the attached “BugRepro” project
2. Select the “Assets/BugDemonstrator.asset” asset
3. Click the "Add Tracking Element" button in the Inspector window
4. Click the “Remove” button in the Inspector window
5. Click the "Add Tracking Element" button in the Inspector window
6. Click the "Modify tracked property" button
7. Observe the Console window
Expected result: Element properties are not tracked once they have been removed
Actual result: “Element 0 is still tracking even though it's been removed.” message is thrown
Reproducible with: 2021.3.39f1, 2022.3.33f1, 6000.0.7f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Add comment