Search Issue Tracker
Duplicate
Votes
0
Found in
5.5.2f1
Issue ID
892119
Regression
No
Texture2DArray.Apply() fails to free texture's system memory after uploading it to GPU
To reproduce:
1. Download and open attached "TestTextureArray2.zip (4.8 MB)" project.
2. Open "main" scene.
3. Enable "LoadTextureArray" object.
4. Build project on any Player (Desktop/Android/iOS).
5. Profile the player with profiler and notice how much total memory uses "Unity" and "GfxDriver".
6. Go back to project and disable LoadTextureArray object.
7. Enable LoadTexture2D object.
8. Repeat steps 4 and 5.
9. Notice the difference in "Unity" memory usage.
Expected result: "Unity" total memory usage should be the same no matter if Loading Texture2Darray or Texture2D.
Actual result: "Unity" total memory usage is significantly bigger when loading texture with Texture2Darray.
Reproduced with: 5.5.3p2, 5.6.1p1, 2017.1.0b5
Reproduced on: Standalone player, iPad Mini 2 (iOS 9.2.1), Samsung SM G903F (GalaxyS5neo)
Notes: Could not test on earlier versions because of shader compilation errors.
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
- Foldout arrow indent is misaligned in the Inspector when used in Custom Type
- [Android] The Player screen turns black when playing a video under certain conditions
- Search window icons at the bottom are cut off when Search window is resized vertically
- "Try something else?" text label is cut off when searching for a long text in the Search window
- Rendering Debugger window sections do not have a minimum width set when resizing with the slider in the middle of the window
This is a duplicate of issue #919162