Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.0f3
2019.4.1f1
2020.1
2020.2
Issue ID
1261859
Regression
Yes
Texture 'Read/Write' option does not double the memory in Profiler
How to reproduce:
1. Open attached project "TextureReadWriteMemory.zip" and scene "test"
2. Open File -> Build Settings
3. Make sure "Development Build" is enabled
4. Build And Run
5. Open Window -> Analysis -> Memory Profiler
6. In Memory Profiler, select the Built Standalone (by default, Editor is selected)
7. In Memory Profiler, press Capture Player
8. Open the snapshot
9. Sort the "Owned Size" data in descending order
10. Observe Native Object Name "2048RW" (should have either 2MB or 4MB)
Expected result: 2048RW takes up 4MB
Actual result: 2048RW takes up 2MB
Reproducible with: 2019.3.0f3, 2019.4.4f1, 2020.1.0b16, 2020.2.0a18
Not reproducible with: 2018.4.25f1, 2019.3.0f2
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
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Resolution Note (fix version 2020.2):
Verified in:
Version: 2020.2.0a20
Resolution Note (fix version 2020.1):
Fixed in 2020.1.1f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.8f1