Search Issue Tracker
Fixed
Votes
0
Found in
2022.3.28f1
Issue ID
UUM-74351
Regression
No
Memory usage is growing in IL2CPP Build when gRPC server is running
How to reproduce:
1. Install ASP.NET Core Runtime and .NET Desktop Runtime from https://dotnet.microsoft.com/en-us/download/dotnet/8.0
2. Open the “MemoryLeak” project
3. Open the “SampleScene”
4. Open the “ServerRuntime” folder locally on your system in the project’s folder
5. Open the “HelloGrpc.exe” file
6. Build And Run the project (File > Build And Run)
7. Open the Task Manager
8. Observe the memory usage of “MemoryLeak.exe” file
Expected result: Memory usage is stable
Actual result: The amount of memory used keeps growing
Reproducible in: 2022.3.28f1
Not reproducible in: 2022.3.33f1, 6000.0.6f1
Fixed in: 2022.3.29f1
Could not test with: 2021.3.39f1 (compilation errors)
Reproducible on: Windows 10, Windows 11 (user’s)
Not reproducible on: No other environments tested
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-69774