Search Issue Tracker
Fixed in 1.7.0
Votes
5
Found in [Package]
1.5.1
Issue ID
1192158
Regression
No
[ScriptableBuildPipeline] Build time increases when building a scene with UseCache parameter set to 'true'
How to reproduce:
1. Open the user attached project
2. Build a project via Test->Build button in a top menu bar
3. Check the elapsed time in the console
4. Build a project once more
5. Compare the build times in both cases
Expected results: Build is faster the second time since assets are not rebuilt
Actual results: The second build is taking longer than the first time (First time ~ 2 minutes; Second time ~ 10 minutes)
Reproducible with: 2018.4.11f1, 2019.2.10f1, 2019.3.0b8, 2020.1.0a9 (package ver 1.5.1, 1.5.2)
Additional notes:
1. The specs of a computer used for testing: i7-8700 3.20 GHz, 16 GB RAM, GTX 1060 6GB
2. If UseCache is set to false, the build takes approx. 2 minutes each time
3. ScriptableBuildPipeline was introduced in Unity 2018.2, therefore a project could not be tested in 2017.4.33f1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 1.7.0):
Fixed in SBP v1.7.0. New preference to enable/disable stripping the detailed debug information from write result before caching. Defaults to enabled for performance.