Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0a3
Issue ID
968482
Regression
Yes
ScriptableObject/MonoBehaviour memory usage increased
Reproduction steps:
- Open attached user project in 2018.1.0a3
- Build Player for Windows with profiler (Architecture x86)
- Run game and inspect how much memory "EmptyScriptableObject" uses.
Expected result: Size will not increase between versions
Actual result: Size usage increases between versions.
Small table:
Unity Player Editor
5.0.4f1 156 B 376 B
2017.1.2p2 172 B 408 B
2017.2.0f2 172 B 408 B
2018.1.0a3 184 B 424 B
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
Add comment