Race condition in the Cache Contracts component #49133

Hello,

We have some race condition with the Cache Contracts component that happen in some case.

I dig in the code and found that the Cache component use the LockRegistry to prevent more than 20 computes at the same time and only one compute per item key.

During the compute of one of our cache an other cache is compute with a different cache key, but if both cache are empty (at least at start) the second one cannot acquire the lock because of bad luck the abs(crc32($item->getKey())) % \count(self::$files) return the same value and then the same lock.

My solution to solve this would be:

• Having the lock only on the item key and not a mix
• Disable the lock per call (but will release all current acquired locks and could have side effect).
• Or The PSR6 cache but lose the lock / stampede feature

What would you recommend to fix those case ?