Search Issue Tracker
Fixed in 2020.1.X
Votes
1
Found in
2018.4
2020.1
2020.1.0a18
Issue ID
1211367
Regression
No
Memory leak occurs when calling socket receive in thread during Play Mode
How to reproduce:
1. Open the "SampleScene" Scene in the attached "1211367.zip" project
2. Open Profiler and click on the Memory Module
3. Enter Play Mode and observe the total system memory usage
Expected result: there's no memory usage rising when executing the script
Actual result: there's a constant memory usage increase
Reproducible with: 2018.4.16f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a21
Could not test with: 2017.4.36f1 (could not compile script due to lower-level version of .NET)
Notes:
-There is a separate c# console .net project attached replicating the code, however, the issue does not reproduce
-Reproducible on Windows
-Not reproducible on Mac
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.1):
Fixed in: 2020.2.0a3