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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment