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
- VisionOS Player and Simulator crashes on "nw_read_request_report [C1] Receive failed with error "No message available on STREAM"" when playing a video through VisionOSVideoComponent
- Shader starts acting unexpectedly when SV_primitiveID is used in a Hull/Domain Shader
- [iOS] "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously when using specific Project Settings and Anti-aliasing is enabled
- Inconsistent help box font size in Project Settings window
- Local package MonoBehaviour scripts appear as missing after updating the project when the project and package paths share the same prefix
Add comment