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
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- 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
Add comment