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
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
- Circle handle of the Game view scale slider bar disappears when the scale is set to 1x
- Asset Bundles non-deterministic behavior with CRCs and hash when a video has Transcoding enabled and Sprite Atlas has an override option enabled
- [Quality Hackweek] Errors "InvalidOperationException: EnsureRunningOnMainThread can only be called from the main thread" and "NullReferenceException" shown when switching build platforms with Muse Texture package installed
- "Importer(DefaultImporter) generated inconsistent result for asset" warnings are thrown when reimporting the "URP" texture
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/