eZ publish will let every session generate a cache block if it does not already exist. This means that after the system has invalidated some cache-blocks, the system will let all HTTP sessions trying to read a cache-block generate the cache-block at the same time.

This will often cause system crashes on high traffic sites.

Attached is a patch which resolves this. The system will now work as following:
1. Check if cache file exists
2. If not, check if another process has started to create the cache file.
3. If another process is creating the cache file, check every second if it's done.
4.a If cache file is generated, use it
4.b If cache file is not generated within 5 seconds, generate it's own.

The patch is based in stable/3.8 rev. 17644