Search Issue Tracker
Third Party Issue
Votes
0
Found in
6000.0.62f1
6000.2.13f1
6000.3.0f1
6000.4.0a2
Issue ID
UUM-127344
Regression
No
WebGL Memory Leaks when unloading a Unity Instance
Steps to reproduce:
1. Create a new Unity project
2. In the Built Profiles window, switch to the Web Platform
3. In the Platform Settings tab, enable “Development Build”
4. Click on the “Build and Run” button
5. Open the build in Google Chrome
6. Open the Dev Tools (right click anywhere on the page with your mouse and select “Inspect”)
7. Navigate to the Memory tab
8. Select "Heap snapshot" and click on the record button once to take a snapshot
9. In the Unity Build, click on the “Unload” button
10. Repeat step 8
11. Compare the two snapshots
Actual results: The second snapshot has the WebGL memory allocated with similar values to the first snapshot
Expected results: The second snapshot has the WebGL memory released
Reproducible with: 6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a2
Could not reproduce with: 6000.5.0a1 (due to the errors when trying to build)
Reproducible on: MacOS 26.0.1 (M4)
Not reproducible on: No other environments tested
Notes:
- The values that aren't releasing the memory: ArrayBuffer, JSArrayBufferData, Context
- A discussion regarding this issue: [https://discussions.unity.com/t/memory-not-freed-when-exiting-the-unity-instance/1691880]
-
The issue reproduces on Google Chrome, Firefox, and Microsoft Edge
- The issue wasn't tested on Safari because its memory profiling tools are less detailed
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
Thank you for bringing this issue to our attention and for taking the time to report it.
Following a thorough review of the reported problem, we have determined that the root cause lies within the Emscripten codebase. We anticipate that this issue will be addressed in a future Emscripten update.
At this time, we will be closing this case. However, we encourage you to monitor upcoming Emscripten releases for relevant updates and improvements.
Thank you again for your valuable feedback and for helping us improve.