Search Issue Tracker
Fixed in 2022.3.34f1
Fixed in 2022.3.X, 6000.0.X, 7000.0.0a9, future release
Votes
1
Found in
2022.3.29f1
6000.0.2f1
6000.1.0a7
Issue ID
UUM-72074
Regression
No
Memory leaks when Instantiating Objects with SerializeReference
How to reproduce:
1. Open the attached Project "testProject.zip"
2. Build and Run a Development Build with the Scene "SampleScene"
3. In the Editor's Menu Bar open Window->Analysis->Memory Profiler
4. Connect the Memory Profiler to the running Build and Capture a Snapshot
5. In the Build, press the "test" Button and wait for "test3" to appear in the Console
6. Capture another Snapshot of the Build
7. Compare the Snapshots
Expected result: both Snapshots show similar/same amount of memory used
Actual result: the later Snapshot shows significantly higher memory usage
Reproducible with: 2021.3.38f1, 2022.3.29f1, 6000.0.2f1
Reproduced on:
- MacBook Pro (2021, M1, MacOS 14.4.1)
- iPhone 7 Plus (iOS 14.6)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment