Search Issue Tracker
Fixed
Fixed in 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment