Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.1.X, 2017.2.X, 2017.4.X
Votes
1
Found in
2017.1.0f3
Issue ID
950574
Regression
Yes
Rising CPU usage when a null assetbundle is being loaded without any indication in the profiler
Steps to reproduce:
1. Open user attached project
2. Run the "Test" scene
3. Spam the "LoadFromCacheOrDownLoad" button
4. Notice the rising cpu usage
Expected result: cpu usage should not rise when a null assetbundle is being loaded
Reproduced in: 2017.3.0a7, 2017.2.0f1, 2017.1.1p2, 2017.1.0b10, 2017.1.0b2, 2017.1.0b1
Not reproduced in: 2017.1.0a6, 5.6.3p3
Regression since: 2017.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment