Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.3.0f4
Issue ID
754465
Regression
Yes
5.3 builds require a larger memory heap than 5.2 builds for WebGL
Steps to reproduce:
1. Open attached project with latest 5.2
2. Build and run for WebGL in development mode with profiler attached
3. When game launches, inspect profiler memory tab
4. Do the same with latest 5.3
5. Compare memory tab in profiler in both versions, notice 'Meshes', 'Animation Clips' and 'Unity' in 5.3 uses roughly twice as much memory as in 5.2
Reproduced with: 5.3.0f4, 5.3.1f1, 5.4.0a6
Not reproducible with: 5.2.4f1
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
Add comment