Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.1.4-preview
Issue ID
1169328
Regression
No
[Addressables] Using Addressable assets results in higher "ShaderLab" memory usage
Reproduction steps:
1. Open "ShaderAndAddressable.zip" project
2. "Build And Run" -> "Without Addressable Assets"
3. Take a Detailed Memory Snapshot
4. "Other" -> "Rendering" -> "ShaderLab" and see how much memory it takes up (10.4 - 13.4 Mb)
5. "Build And Run" -> "With Addressable Assets"
6. Take a Detailed Memory Snapshot
7. "Other" -> "Rendering" -> "ShaderLab" and see how much memory it takes up (18.4 - 22.8 Mb)
8. Compare the two memory snapshots
Expected Result: Both have similar memory usage
Actual Result: Using Addressables increases the memory usage of ShaderLab
Reproduced with: 2019.3.0a10, 2019.2.0b10, 2019.1.11f1, 2018.4.5f1
Note:
Setting "Project Settings" -> "Graphics" -> "Shader Stripping" -> "Fog Modes" -> "Custom" to "Linear" makes both builds use the same amount of memory. (Both have the bigger memory usage)
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
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Resolution Note:
Please see Ryan's notes. If the customer can not manage the override function as Ryan suggested, please have them contact their support person to help with this issue.