Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
4.5.0f6
Issue ID
611705
Regression
No
Repeated Set/GetPixels calls increases memory use by application
To reproduce:
1) Open attached project and scene inside it.
2) Open up something to capture RAM amount like Task or Process Manager.
3) Play the scene.
4) Each Spacebar press activates script which destroys texture and then generates it back. Notice how after each click the memory increases by about 350 MB but then stops to grow after about 5 generations.
Stopping game keeps that RAM. Starting scene again does not add any extra leak though.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment