blob: properly respect max size when copying blobs
CopyFileContentsWithOffsetAndSize takes in a max size, but uses the wrong variable to consider how much is remaining to read, and so ends up reading the entire file (rather than limiting to size). Because of this, there's a size mismatch in the calling function and the blob fails with kInvalidBlob. This should fix some of the errors from issue 1114200. I also see out of memory errors, but those make more sense than this logic error. Bug: 1114200 Change-Id: I6d8f371655e38bdd02cc89e9d524de757e1c202a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2392987 Commit-Queue: enne <enne@chromium.org> Reviewed-by:Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#804477}
Showing
Please register or sign in to comment