> > Jon do you think it could be a memory or storage issue? > Almost certainly not a storage (as in disk or remote s3) issue since the local disk is not exhausted and there is no evidence of an S3 access issue.
Based on the fact that a call to gdal.VSICurlClearCache appears to clear the symptom, it does look like a corruption of the in-memory VSICurl cache (or, more likely, its book-keeping data structures). I suspect Thomas is correct and the issue will be fixed in gdal-2.4.4 (by the fix for https://github.com/osGeo/gdal/issues/1244) but it is too early for me to say for sure yet. jon.
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
