Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4.17f1
Issue ID
1368302
Regression
No
[WebGL] Memory leak when using custom stack data type and allocating a large array
Reproduction steps:
1. Download and open the "myvegas_source_webgl_memory_leak_9_22" project from the google drive link
2. Open the "Main" scene
3. In the menu bar, press "MyVegas" > "Build"
4. In the Custom Build System window, press "PREPARE ENVIRONMENT"
5. In the "AppConfig" window, change "SocialAuthStrategy" to "Optional" and click "Save"
6. In the Custom Build System window, press "BUILD PLAYER", and then "BUILD STREAMINGBUNDLES"
7. In the WebGL player window, click and hold the "Spin" button
8. Observe the Profiler window,
Expected result: Total and reserved memory does not progressively grow
Actual result: Total and reserved memory starts progressively growing
Reproducible with: 2019.4.17f1, 2019.4.31f1
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2022.1.X):
This is a limitation of the WebGL platform and mentioned in the documentation. https://docs.unity3d.com/Manual/webgl-memory.html