Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1p3
Issue ID
919439
Regression
No
Baked GI of unloaded scenes is still loaded to RAM
Steps to reproduce:
1. Download 919439 repro.zip
2. Build Lightmaps for all 5 scenes in the project
3. Build to iOS or Standalone (OSX/Windows) or Android with all 5 scenes included in the build
4. Run the app
5. Observe how much RAM is being used
6. Build the app with only "Prison" scene included in the build
7. Compare the RAM usage with the previous build
Expected results: RAM usage is the same in both builds, since only a single scene is loaded in both cases.
Actual results: RAM usage with 5 scenes built is around 5MB higher.
Reproduced on: 5.5.3p4, 5.6.1p3, 2017.1.0b8
Reproduced with: iPad 2 Mini (iOS 10.3.1) OpenGLES2/Metal, MacBook Pro (Retina, 15-inch, Mid 2015, macOS 10.12) Metal, Windows 10 DirectX 11, Samsung SM G950U (Android 7.0) OpenGLES3
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This issue has been identified as having low priority and has been closed without a fix. If the bug has no workaround and is blocking your production please feel free to reopen it with any additional information you might have. Sorry for the inconvenience this might cause.