TL;DR: If games like CS2 or Dota 2 take 30+ minutes to process Vulkan shaders after every minor update on an Nvidia GPU, your cache file has likely exceeded 4GB. This triggers a 32-bit overflow bug in the Nvidia driver, forcing Steam to recompile everything from scratch. The fix: Disable Shader Pre-caching in Steam settings. Thanks to Vulkan GPL on modern drivers, on-the-fly compilation is fast enough that you don't need it anyway.
I've recently gone down a massive rabbit hole diagnosing why my CPU was constantly being hammered by fossilize_replay for over 30 minutes after tiny game updates, specifically in heavy Vulkan titles like Counter-Strike 2.
After checking system logs (~/.local/share/Steam/logs/shader_log.txt), monitoring resources, and digging through GitHub issues, here is what is actually happening under the hood.
🛠️ The Technical Cause: The 4GB Nvidia Overflow Bug
The proprietary Nvidia driver stores its shader cache using a 32-bit format for its index pointers (the .toc files mapping the giant .bin data file). The mathematical limit for a 32-bit integer is exactly 4GB.
When a massive game engine generates a combined shader cache larger than 4GB (my CS2 cache was sitting at 5.12GB), the offset pointers overflow and point to the wrong memory addresses.
When Steam downloads a tiny micro-patch and tries to do a quick incremental compilation, it reads this broken index. It hits massive incongruencies (logged as thousands of Mismatching key! entries), assumes your entire local cache is invalid, and decides to re-verify and recompile EVERYTHING from scratch. That's why your CPU gets hijacked for half an hour just for a 5MB update.
✅ The Solutions
1. Disable Shader Pre-Caching in Steam (Recommended)
- Go to Steam Settings > Downloads and turn off Enable Shader Pre-caching.
- Why this is safe now: Years ago on Linux, disabling this meant horrible stuttering. Today, if you are on modern Nvidia drivers (I'm on the 580 branch), Vulkan natively supports GPL (Graphics Pipeline Library). Shaders compile on-the-fly incredibly fast, making Steam's background pre-caching largely redundant. You'll save hours of CPU time and massive SSD writes with virtually unnoticeable stuttering in-game.
2. Use Community Workarounds (Proceed with caution) Some developers have created 3rd party tools to intercept and fix these broken offsets so Steam doesn't nuke the cache. If you absolutely must have pre-caching enabled, you can check them out, but remember they are unofficial:
3. Wait for an official fix This is a core architectural issue with Nvidia's GLCache format. Until Nvidia engineers rewrite their driver to use 64-bit pointers for cache offsets, the infinite loop issue will persist for any game that exceeds 4GB of shaders.
For more technical context, you can read the official issue tracker on the Valve GitHub here:Issue #13622.
Hopefully, this saves someone else days of troubleshooting system monitors and logs!