Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
1
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.0f1
2019.3.0a1
2020.1.0a1
Issue ID
1176913
Regression
No
High CPU Load when editor is trying to trim Full GI Cache
How to reproduce:
1. Create and open a new project
2. Ensure "Maximum Cache Size" (in Edit -> Preferences) is set to 5GB,
3. Close project,
4. Fill your GI Cache by pasting the following files into your cache location: https://drive.google.com/open?id=1Q5IDUH0Xv_Fg6ZjxD8LdfXvgCbE1DQVe
3. Reopen project and check the CPU usage in the Task Manager,
4. Quit the Editor and check Editor.log for TrimDiskCacheJob (or GIFileCache::OnRemoveFile logs only on LTS)
Expected Behaviour: The GI Cache is trimmed and CPU usage is low after the trim
Actual Behaviour: The GI Cache is not trimmed and TrimDiskCacheJob (GIFileCache::OnRemoveFile) is constantly working
Reproducible with: 2017.4.32f1 2018.4.8f1, 2019.2.2f1, 2019.3.0b1, 2020.1.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment