Search Issue Tracker
Duplicate
Votes
0
Found in
2020.3
2020.3.19f1
2021.1
2021.2
2022.1
Issue ID
1377696
Regression
No
Mesh memory footprint is larger than estimated when profiling with the Profiler API
How to reproduce:
1. Open the user-submitted project
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
- Separation lines between minimized fields become invisible when scrolling in the Profiler
- Drag & drop and object picker assignment fail when ExposedReference variables are used in a Timeline clip
- AudioSource.time prints out 0 when AudioSource is not playing even if it is manually set
- [Android] Crash on "UnityMotionEventCallbacks::_GetPointerIdImpl" when giving 8 simultaneous touch inputs
- "[Header]" attribute is misaligned when placed before an InputActionProperty field
This is a duplicate of issue #1339862