Comment #8 on issue 6522 by [email protected]: [UMR] Uninitialized memory read in fwrite_nolock http://code.google.com/p/chromium/issues/detail?id=6522
The problem here is that we seem to be calling NotifyReadComplete(10240) in URLRequestSlowDownloadJob::CheckDoneStatus() and that ends up sending 10240 bytes of junk first and then actually reads those 10240 bytes (and they get sent as well). I don't think we should be calling NotifyReadComplete because the read is yet to be done but I don't know whats the alternative (we want to trigger a read to finish up a download that is paused). The problem is in the test framework so I don't know whether we want to keep the stable tag. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
