Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
0
Found in
2020.3
2020.3.8f1
2021.1
2021.2
2022.1
Issue ID
1339862
Regression
No
Mesh memory footprint is larger than estimated when profiling with the Profiler API
How to reproduce:
1. Open the attached project "MeshMemoryUsage"
2. Open the scene "SampleScene" and enter Play mode (Assets/Scenes/SampleScene.unity)
3. In the Game view, click the "Generate Mesh" button
4. Observe the _expectedTotalSize and _resultingSize values under the button
Expected result: _expectedTotalSize and _resultingSize display similar values
Actual result: _expectedTotalSize value is 2x smaller than _resultingSize
Reproducible with: 2020.3.22f1, 2021.1.28f1, 2021.2.1f1, 2022.1.0a3
Not reproducible with: 2022.1.0a4, 2022.1.0a14
Could not test with: 2019.4.32f1 (Script errors: 'Mesh' does not contain a definition for 'AllocateWritableMeshData', 'ApplyAndDisposeWritableMeshData', The name 'useDots' does not exist in the current context)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a4
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.8f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.26f1