See  crbug.com/472740  for details.
The http cache lock was fixed for full(non-range) requests as part of that issue. This is a placeholder for any discussions regarding the resolution for the cache lock for range requests so that the original bug can be marked as fixed.

The issue is non trivial to be fixed for range requests since currently HttpCache::Transaction state machine goes back to headers phase repeatedly for serving different ranges of the range request. That does not align trivially to the cache lock fix and needs an involved design phase to understand the alternatives.