Search Issue Tracker
By Design
By Design in 6000.2.X
Votes
0
Found in
2021.3.45f1
2022.3.53f1
6000.0.31f1
6000.1.0a8
6000.2.0a1
Issue ID
UUM-90456
Regression
No
[IL2CPP] Extremely high memory usage when building for Linux platform
Reproduction steps:
1. Open the attached “IN-90045” project
2. Open the Build Settings window (File > Build Settings)
3. Make sure “Linux” is the selected platform
4. Make a Clean Build of the project
5. Observe the Build progress
Expected result: The Build finishes successfully
Actual result: Memory usage keeps increases on “Linking GameAssembly.so (x64)” task
Reproducible with: 2021.3.45f1, 2022.3.53f1, 6000.0.31f1, 6000.1.0a8
Reproducible on: Ubuntu 24.04, Windows 10, Arch (user)
Note:
- On Linux machines with lower amount of RAM, the task is terminated by OOM killer.
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
- 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
Resolution Note:
I will mark this as designed, as the issue is caused by the C++ Compiler configuration being set to Master. As stated in the documentation: "Master configuration enables all possible optimizations, squeezing every bit of performance possible. For instance, on platforms that use the MSVC++ compiler, this option enables link-time code generation. Compiling code using this configuration can take significantly longer than it does using the Release configuration. Unity recommends building the shipping version of your game using the Master configuration if the increase in build time is acceptable."
Resolution Note (6000.2.X):
I will mark this as designed, as the issue is caused by the C++ Compiler configuration being set to Master. As stated in the documentation: "Master configuration enables all possible optimizations, squeezing every bit of performance possible. For instance, on platforms that use the MSVC++ compiler, this option enables link-time code generation. Compiling code using this configuration can take significantly longer than it does using the Release configuration. Unity recommends building the shipping version of your game using the Master configuration if the increase in build time is acceptable."