{"push_id":660327701,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"205d67152e8f8fe221afe9bd17763877095969df","before":"548c426a8f4b1b294d0a22e049c5df4df21e75fc","commits":[{"sha":"802697253818b376006a0edf26fbd6dbcd4b773f","author":{"email":"dce7183dd721072d236fed9264529050987c94bf@gmail.com","name":"Caleb Spare"},"message":"s3manager: Fix memory leak\n\nBefore this fix, s3manager was holding onto the entire contents of the\nio.Reader that it's uploading.\n\nEach work chunk is\n\n  type chunk struct {\n    buf []byte\n    num int64\n  }\n\nand the list of completed parts is []*s3.CompletedPart which include\n\n  PartNumber *int64\n\nWhen the new completed part is created using &c.num for the PartNumber,\nthe pointer means that the whole surrounding chunk, including the\nbuffer, is still live as far as the collector is concerned.\n\nThe fix is simple: copy num.","distinct":true,"url":"https://api.github.com/repos/awslabs/aws-sdk-go/commits/802697253818b376006a0edf26fbd6dbcd4b773f"},{"sha":"205d67152e8f8fe221afe9bd17763877095969df","author":{"email":"be97ac84963a82296fd1ab1af6358dfaa6463b0a@soen.ca","name":"Loren Segal"},"message":"Merge pull request #226 from cespare/s3manager-fixes-1\n\ns3manager: Fix memory leak","distinct":true,"url":"https://api.github.com/repos/awslabs/aws-sdk-go/commits/205d67152e8f8fe221afe9bd17763877095969df"}]}