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
- The "Build and Run" Menu option tries to build for the selected Build Platform instead of the Active Build Platform
- Font kerning breaks at runtime when multiple UI Documents use different fonts
- MissingReferenceException occurs when entering Play mode with a locked GameObject in the Inspector
- [URP] Crash on GameObject::QueryComponentByType when accessing a component from an unsaved template created scene
- Return value and out parameter get scrambled when a Custom HLSL Operator is used
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a13
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.1f1