Search Issue Tracker
By Design
Votes
1
Found in
5.3.5f1
Issue ID
811312
Regression
No
[WebGL] Potential huge memory leak
Steps to reproduce:
1. Open attached project.
2. Select "WebGL" as a target platform ("File->Build Settings->Web GL->Switch Platform").
3. Enter the Play mode and wait until all the scenes are being uploaded.
4. Click on the "Start" button.
5. Click on the "View the Gallery" icon (second icon from the top on the left).
6. Click on the word "Knee".
7. Click on any of the five icons that open up below the word "Knee".
8. Notice that the model in the main viewing area changes.
9. Open the "profiler" window or "Task manager", try repeating the 7th step several times and observing the memory usage of "Unity Editor".
Actual result:
The memory usage of "Unity Editor" increases by 3-10 megabytes after every click.
Expected result:
The memory usage of "Unity Editor" should be consistent on "Web GL".
Reproduced with:
5.3.5f1, 5.3.5p6, 5.4.0b25.
Cannot reproduce with:
5.1.0f3, 5.2.4f1, because of Unity Analytics: "The name `Analytics' does not exist in the current context".
Note:
The same result might be achieved by building for "Web GL", opening the build with a browser and repeating the steps provided earlier.
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
kamstar
Aug 18, 2016 14:14
We have the same problem on 5.4.0b25