Search Issue Tracker
Fixed in 2018.2.0b5
Votes
0
Found in
2017.2.0b8
Issue ID
945533
Regression
No
UnitySplash-Cube stays in memory even after splash screen
To reproduce:
1. Open attached Unity project "BugReport_UnitySplash-Cube_StaysInMemory.zip"
2. Go to build settings and check "Development Build|
3. Build the game and run it
4. Window --> Profiler
5. Click Connected Player --> WindowsPlayer
6. Click on Memory profiling
7. Click on "Simple" and change it to "Detailed"
8. Click on Take Sample: WindowsPlayer
9. Navigate to Built-in Resources --> Texture2D
Expected result: There should not be UnitySplash-cube process after the splash screen is finished
Actual result: UnitySplash-cube process keeps on working in the background
Note: reproducible on every project
Reproduced on: 5.6.3f1, 2017.1.0p5, 2017.2.0b9. 2017.3.0a6
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
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
DrunkenMastah
Jun 23, 2018 05:41
That texture is 10.7 MB on my iPhone5C. Not good when my total limit is so low as well.
Please fix this. I hope this is not the same in release builds??