Search Issue Tracker
Won't Fix
Votes
11
Found in
2023.1.0a6
2023.2.0a1
2023.3.0a3
Issue ID
UUM-1139
Regression
No
[WebGL] Player's memory is not released when calling Quit function on Unity Instance with Decompress Fallback enabled
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Go to the Publishing Settings (Edit->Project Settings->Player->Publishing Settings)
3. Make sure that "Compression Format" is selected and "Decompression Fallback" is enabled
4. Make a WebGL build
5. Open the WebGL Player in a browser
6. Press the "Launch Unity" button (**WARNING** Don't wait for the Player to fully load as it freezes up the system)
7. Press the "Quit" button
8. Take a Memory Snapshot (press the shortcut F12 and go to the Memory tab)
9. Inspect the used Memory size
10. Repeat from the 6th step a few times (2-3)
Expected result: Memory is released after quitting from the WebGL Player
Actual result: Memory is not released after quitting from the WebGL Player
Reproducible with: 2020.2.5f1, 2021.1.0b7, 2021.2.0a6
Couldn't test with: 2018.4.32f1, 2019.4.20f1 ("Decompress Fallback" option is not available)
Note: Not reproducible with no compression and "Decompress Fallback" disabled
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
- SpeedTree does not move when using WindZone
- "Undeclared identifier 'LinearToSRGB'" error is thrown when creating a color variable with HDR color mode and assigning a Custom Render Texture target in Shader Graph
- Input System package is missing when creating a new HDRP project
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.