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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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/