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
- "Shader error in 'Shader Graphs/Master': invalid subscript 'texCoord6' at /(243) (on d3d11)" error thrown when UV2-UV7 is connected to Base Color In Fullscreen Shader Graph
- [Linux] Navigating Prefab Components in Overrides window shows rendering artifacts in the Editor
- Prefab Overrides window cuts-off Component labels across multiple Components
- Opening Memory Settings documentation from Project Settings window opens missing page
- Animated GameObjects ignore Shader keywords when running on VisionOS Player with Polyspatial
Resolution Note (fix version 2020.1):
Fixed in: 2020.2.0a3