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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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