Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2019.2.6f1
2019.4
2020.1
2020.2
2021.1
Issue ID
1188667
Regression
Yes
[WebGL] Memory is not released when on Application Quit
How to reproduce:
1. Open the attached project's "case_1188667-Project.zip" Scene labeled "SampleScene"
2. Make a WebGL build
3. Host the WebGL build
4. Open the built WebGL Player in a browser
5. In the Player, press the "Quit" button
Expected result: Message is logged in the Developer Console that Player has quit
Actual result: Browser throws a "RuntimeError: memory access out of bounds" error or there's an "ArgumentNullException: Value cannot be null" error in the Developer Console
Reproducible with: 2019.4.17f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0a1
Not reproducible with: 2018.4.30f1, 2021.1.0a2, 2021.1.0b1
-
aaniceto
Aug 23, 2021 19:39
I see this bug also in 2020.3 LTS, which seems an important bug from where we stand. It's really important for our project.
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
- UI Builder - Transitions on elements with hover are only applied the first time hover occurs
- Unity drains raw input message queue before Rewired can process each event, making it miss some
- Old input system misses some mouse movement if the new input system is also enabled
- [URP] _ProjectionParams.x with Overlay rendering
- Thumbnails in a Project window get darker after reimporting assets
Resolution Note (fix version 2021.1):
Fixed a bug where calling unityInstance.Quit() from JavaScript (and releasing all references to unityInstance) would not let JS VM garbage collect away the Unity game application. Fixed in Unity 2021.1.0a2 and above