Search Issue Tracker
Fixed
Fixed in 6000.5.0a6
Votes
0
Found in
6000.4.0b5
6000.5.0a5
Issue ID
UUM-133100
Regression
Yes
Memory leak warnings are thrown when saving a dirty scene with world space UI that has a label
How to reproduce:
1. Open the attached “IN-130675.zip” project
2. Open the “Main” scene
3. Move a GameObject so the scene is marked dirty
4. Save the scene
5. Observe the console
Actual result: Memory leak warnings are thrown
Expected result: No warnings are logged in the console
Reproducible with: 6000.4.0b5, 6000.5.0a3, 6000.5.0a5
Not reproducible with: 6000.0.66f1, 6000.3.5f1, 6000.5.0a2
Reproducible on: MacOS Sequoia 15.7.3 (M1 Max)
Not reproducible on: No other environments tested
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
- GameObjects change Hierarchy order when undoing adding Component to multiple GameObjects
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.
We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.
Thank you for helping us improve Unity!
Resolution Note (fix version 6000.5.0a6):
Thank you for reporting a bug to Unity.
We have reviewed the issue and found it is a duplicate of an existing bug already logged in our system. To keep things organized and ensure the issue is properly prioritized, we have linked your report to the original case.
We will now close this report as a duplicate, but the original bug remains open and under review. Your input has been noted and helps us better understand the impact of the issue. If anything changes regarding its severity or impact, please let us know.
Thank you for helping us improve Unity!