Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.3.X, 2022.1.X
Votes
0
Found in
2020.3
2020.3.19f1
2021.1
2021.2
2022.1
Issue ID
1377773
Regression
No
Memory Profiler reports wrong Mesh size results when generating it with JOBS
How to reproduce:
1. Open the user's attached "MeshMemoryUsage" project
2. Open the "SampleScene" Scene
3. Enter the Play Mode
4. Select the "Generate Mesh" button in the Game View
5. Compare the "_expectedTotalSize" and "resultingSize" values
Expected result: The "_expectedTotalSize" value calculated in the user's script matches the Memory Profiler "resultingSize" reported value
Actual result: The values differ ~200 times
Reproducible with: 2020.3.19f1, 2021.1.28f1, 2021.2.1f1, 2022.1.0a14
Couldn't test with: 2019.4.32f1 (user script error related with method nonexistence in earlier versions)
Note: Disabling the "GameObject -> Mesh Oddness Repro (Component) -> Use Dots" boolean value generates Mesh in other method, where the "_resultingSize" value is almost twice higher than "_expectedTotalSize"
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
- Sprite Atlas remains loaded in memory after scene change or unloading assets
- Decompressing a DeflateStream under IL2CPP misses a few bytes
- Referred style sheet stays dirty after saving when using the UIBuilder
- The Height map Amplitude is not working when using HDRP/LayeredLit
- Infinite inertial tensor rotation values are not discarded (both AB and RB)
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a3
Resolution Note (fix version 2022.1):
Fixed in 2022.1.2f1
Resolution Note (fix version 2021.3):
Fixed in 2021.3.3f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.38f1