Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
2017.1.0f3
Issue ID
946442
Regression
Yes
Editing UI Text in Play mode with script causes Memory Leak (~30mb/s)
How to reproduce:
1. Download attached project file
2. Open "Intro" Scene and press Play
Actual result: Memory usage climbs rapidly (about 30 megabytes per second) and eventually will crash with an Out Of Memory error. Stopping the scene does not free the memory. The profiler shows that Mono memory is stable and small. The "Unity" memory climbs very rapidly.
Reproduced with: 2017.1.1f1, 2017.2.0b9, 2017.3.0a2
Not reproduced with:5.5.4p3, 5.6.3p2, 2017.3.0a3, 2017.3.0a6
Regression since: 2017.1.0a1 till 2017.3.0a2
Comments (1)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Peter77
Sep 23, 2017 00:50
The related forum thread is:
https://forum.unity.com/threads/2017-2-case-939424-shared-ui-mesh-memory-leak.486912/