Search Issue Tracker
Duplicate
Votes
0
Found in
5.4.0f3
Issue ID
822637
Regression
No
Memory Leak appears when entering play mode with two cameras and UI element
Steps to reproduce:
1. open ExampleProject
2. open scene "ExampleScene"
3. Press play
4. Open Profiler
5. Choose Memory tab
Result: notice how used memory is increasing.
Reproduced with: 5.5.0a5, 5.4.0f3, 5.3.6p2,
Not reproduced with: 5.2.5f1 (there is no Target Display settings)
Note:
-Adding more Canvas elements or cameras increases used memory growth
-Example Project has 2 cameras (both Target Display settings are different)
-Canvas Render Mode is set to World Space
-You can see creation of the project in a video attached by user (link).
Comments (2)
-
whiskers434
Dec 20, 2016 03:32
Reproduced in 5.4.1f1, 5.50f3 - 20th Dec 2016
plz fix thanks
-
bradleyhean1
Sep 29, 2016 19:58
I hope this is indeed a duplicate as stated because I too get this same thing happening as the OP without GoogleVR
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #819470