Search Issue Tracker
Fixed in 2020.1.X
Votes
19
Found in
2018.2.0b10
Issue ID
1054493
Regression
No
[Windows] Memory leak on .Net 4.x and x86 builds
To reproduce:
1. Download attached project "MemoryUsage.zip" and open in Unity
2. Open "SampleScene" scene
3. Enter Play mode
4. Observe that Memory usage is within 200 MB
5. Exit Play mode
6. Change Scripting Runtime Version to ".NET 3.5 Equivalent" and Scripting Backend to "Mono"
7. Set Target Platform to "Windows" and Architecture to "x86_64"
8. Build And Run
9. Observe that Memory usage is within 200 MB
10. Set Architecture to "x86"
11. Build And Run
12. Observe that Memory usage is within 200 MB
13. Change Scripting Runtime Version to ".NET 4.x Equivalent"
14. Set Architecture to "x86_64"
15. Build And Run
16. Observe that Memory usage is within 200 MB
17. Set Architecture to "x86"
18. Build And Run
Expected result: You will see that Memory usage is still within 200 MB
Actual result: You will see that Memory usage allocates up to 3GB until it produces "out of memory" exceptions
Notes:
- This issue reproduces only on Windows
- If you set Scripting Backend to "IL2CPP" and Architecture to "x86", the build will crash
Reproduced on Unity 2017.1.4p2, 2017.2.3p2, 2017.3.2f1, 2017.4.6f1, 2018.1.7f1, 2018.2.0b11 and 2018.3.0a3
Comments (11)
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
- Previous model to world matrix is not correctly set for ASW
- More calls are made to GC.Alloc in an HDRP Sample Template when compared to the 2022.3 stream
- Generating Light Probe lighting returns inconsistent results on a specific mesh
- Two Warnings appear for every Soft Delete Operation when Deleting Sub Assets in the Project Browser
- “Item m_LightProbeSystem not found” warning is thrown when pressing the “Open” button multiple times in the Adaptive Probe Volume component warning
DylanKliment
Sep 18, 2018 14:13
This is also reproducible in 2018.2.8f1 and .6f1