Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0f3
Issue ID
930718
Regression
Yes
[Regression][MemoryLeak] Mesh memory increases when reenabling images under the canvas
To reproduce:
1. Open project attached by QA
2. Make sure that "test_scene" is opened
3. Hit play and inspect profiler (focused on the memory)
4. Notice that mesh memory increases
Expected: After some time mesh memory should stabilise and remain still.
Actual: Mesh memory increases all the time till build/editor crashes.
Reproduced with: 2017.1.0a1, 2017.1.0f3, 2017.2.0b3
Not reproduced with: 5.6.2p3
Regression since 2017.1.0a1
Issue is cross platform, reproduced with: iPhone 7+ 10.3.2; Google Nexus 6*, OS:6.0.1, CPU:armeabi-v7a, GPU:Adreno (TM) 420.
To reproduce on builds enable development build and autoconnect profiler. After build starts in Unity select profiler window and click on connected player and select your device.
Note: If you disable development build and autoconnect profiler on builds memory leak disappears.
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
- [UI Builder] Viewport's gizmos for Margin and Padding disappear when dragging to modify the value and the cursor leaves the Spacing section
- "Multiplayer Center" window does not reflect changes made in "Other Packages" section
- Crash on D3DKMTOpenResource when capturing with RenderDoc while GPU Skinning is set to GPU(Batched)
- Editing and saving Curve changes in UI Builder window throws multiple errors in the Console
- [UI Builder] Value is not selected when left clicking on Spacing/Border Widget values
This is a duplicate of issue #912789