If the files to store in S3 are malformed, then an infinite loop can exist when writing metadata.
In my case, I have a lot of private files for some reason:
private://.htaccess
private://feeds/cache/445527d5e6fcd40b2eff83cfe8770b0fb424fab61f85a888b7dc72a423fa5af8
private://feeds/cache/845b7e89a4201f988d10504f07e13a3be9d945fc4e278a51f34fb1dc64365848
private://feeds/cache/aefce71fac999df34d3be4faf9707d56496bfede8265f08c99e9c8fa32bfce1e
private://feeds/cache/dc482c4f6c79b0efcb597b3f74f8663ce71c7b7b575e26f8275b671d975bd623
private://feeds/cache/e097ef31ce573c15b0434f8cfbf20e63f1bf7b0bd8fc2eb66d9544f24a303c97
private://feeds/cache/e14c49f73ed98b63b9411868f5536d7cf0c5f3ec3571a680060d75d19ea5acf2
private://feeds/cache/e86f13a64ec61103905694ef151fe916285dab54eb70d82d88133faa0d3dae74
private://feeds/in_progress/FeedsHTTPFetcherResult1562230834
private://feeds/in_progress/FeedsHTTPFetcherResult1562230834_0
Do a check for an infinite loop:
Closed: outdated
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Drupal 7 end-of-life triage:
Drupal 7 reached end of life on January 5th.
The 7.x branches of S3FS do not have any additional planned releases.
The requests in this issue do not appear to exist in the 8.x-3.x and newer branches.