Search Issue Tracker
Fixed in 2021.1
Fixed in 2019.4
Fix In Review for 2020.2
Votes
0
Found in
2018.4
2019.3.9f1
2020.2
Issue ID
1268289
Regression
No
Meshes with enabled Read/Write option report their memory consumption incorrectly
How to reproduce:
1. Open user-submitted project (DoubleMemoryMesh.zip), SampleScene
2. Make a development build with the 'joker_thief_RW' in the scene
3. In the scene replace 'joker_thief_RW' with 'joker_thief' and make another development build
4. Open each build, attach Unity profiler and take a detailed memory sample
5. Compare the memory report of Assets/Mesh for both builds
Expected result: model with Read/Write enabled reports memory consumption correctly
Actual result: model with Read/Write enabled either reports identical memory consumption as without R/W or only a slight increase(~0.2MB)
Reproducible with: 2018.4.26f1, 2019.4.8f1, 2020.1.3f1, 2020.2.0a21
Notes:
Tested on macOS
Newest versions of Unity report higher memory consumption for R/W models, but only marginally(0.2 MB difference); may still be incorrect
2018.4.26f1 - Read/Write disabled: 2.2 MB
2018.4.26f1 - Read/Write enabled: 2.2 MB
2019.4.9f1 - Read/Write disabled: 1.8 MB
2019.4.9f1 - Read/Write enabled: 2.0 MB
2020.1.3f1 - Read/Write disabled: 1.8 MB
2020.1.3f1 - Read/Write enabled: 2.0 MB
2020.2.0a21 - Read/Write disabled: 1.8 MB
2020.2.0a21 - Read/Write enabled: 2.0 MB
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
- Shader error db grows on each build
- Android ARCore build fails with 2019.4 due to outdated Gradle
- [tvOS] Visual artifacts are present when Ambient Occlusion is enabled and Dynamic Resolution is reduced
- Texture Importer Inspector throws errors when a built-in texture inspector is overwritten in C#
- Invalid AABB error is thrown when moving a Particle with Velocity over Lifetime and Limit Velocity over Lifetime modules
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a9