Search Issue Tracker
Fixed in 2018.2.X
Votes
1
Found in
2017.2.0f2
Issue ID
960554
Regression
No
Splash screen resources are not unloaded from memory
To reproduce:
1. Open project attached by QA
2. Open build settings and attach "test" scene
3. Make sure that splash screen is disabled (Edit -> Project Settings -> Player -> splash image)
4. Build and run project on WebGL
5. After build opens in the browser, enable JavaScript console and click "Log Now" button
6. In the console notice "Memory used" text and value of memory that is used
7. Repeat the same steps but with enabled Splash Screen
Expected result: Memory usage should be pretty much the same in both situations (splash screen should be unloaded from memory).
Actual result: Memory usage is almost twice bigger when using splash screen
Reproduced with: 5.6.4p1, 2017.2.0f3, 2017.3.0b5, 2018.1.0a1
Comments (3)
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Rob-Fireproof
Jan 17, 2020 16:36
Still a problem in 2018.4.14
neowedge
Jul 23, 2019 11:45
I reproduced it with Unity 2018.4.2 and 2018.4.4 (I didn't test it on other versions) over an Android build.
I can see the splash screen logos with Unity Profiler, using take sample option (on detailed memory section).
IamWind
May 24, 2018 02:26
Is there any solution to workaround for Unity version lower than 2018.2 ?