Search Issue Tracker
Fixed
Fixed in 1.4.X - Entities
Votes
0
Found in [Package]
1.4.0-pre.3 - Entities
Issue ID
ECSB-1741
Regression
No
Memory leak when calling the SerializeUtility.SerializeWorld function
How to reproduce:
1. Open the attached “IN-104975” project
2. Open the “SampleScene”
3. In the Hierarchy, select the “Canvas” GameObject
4. In the Inspector, make sure the “Wrong Allocator Demo (Script)” Component is disabled
5. Enter Play mode
6. Observe the result in the Console window
Expected result: The memory is stable
Actual result: The memory is increasing
Reproducible with: 1.2.1 (2022.3.65f1), 1.4.0-pre.3 (2022.3.65f1, 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Note:
If the memory leak message is not appearing in the the Console window, complete the following:
1. Enable the “Wrong Allocator Demo (Script)” Component and the “Fix” checkbox and enter Play mode
2. Exit Play mode, disable the “Fix” checkbox
3. Enter and exit Play mode
4. Disable the “Wrong Allocator Demo (Script)” Component and enter Play mode
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note (fix version 1.4.X - Entities):
Fixed in next version of Entities.