Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2019.4
2019.4.22f1
2020.3
2021.1
2021.2
Issue ID
1338754
Regression
No
[UWP] Memory leak when creating BitmapDecoders using MemoryStreams
How to reproduce:
1. Open the attached "Il2CppMemLeakSampleDesktop.zip" project
2. Build the "SampleScene" Scene to UWP
3. Open Visual Studio solution
4. Deploy the solution to Hololens 2 (with ARM64 Remote machine deploy settings) and launch profiler
5. Press the button with the text "Create ImageDecoders" -> Observe the memory usage on the profiler -> Press the same button multiple times
Expected result: Memory leak does not occur
Actual result: Memory leak occurs every time the button is pressed
Reproducible in: 2019.4.28f1, 2020.3.8f1, 2021.1.10f1, 2021.2.0a19
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a13
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.1f1