Search Issue Tracker
Fixed in 6000.0.54f1
Fixed in 6000.0.X, 6000.1.X, 6000.2.X, 6000.3.X, 6000.3.0a2
Votes
0
Found in
6000.0.49f1
6000.1.9f1
6000.2.0b7
6000.3.0a1
Issue ID
UUM-109369
Regression
Yes
Memory address leaks when using Visual Elements in a specific project
How to reproduce:
1. Open the attached project UUM-109369.zip
2. Open the SampleScene and enter Play ModeSearch
3. Click "Add Children", "Clear", "GC.Collect" and then "Find Refs"
4. Observe the TextField contents
Expected result: TextField says "Found 0 unexpected elements."
Actual result: TextField says "Found 10 unexpected elements." or some other >0 number
Reproducible with: 6000.0.39f1
Not reproducible with: 6000.0.38f1
Reproduced on: macOS 15.5 (user reported)
Not reproduced on: No other environment tested
Note: If bug doesn't reproduce on first try, try clicking Add Children a few times and then Clear, Collect and Find Refs again. It usually reproduces on the first or second try.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
Add comment