Issue 3497: Improper cancellation of a FileInputStream operation.
http://code.google.com/p/chromium/issues/detail?id=3497
New issue report by [EMAIL PROTECTED]:
URLRequestFileJob::Kill has the following code:
stream_.Close()
and the implementation of FileInputStream::Close does:
CloseHandle(handle_);
async_context_.reset();
The problem with this code is that if there is an IO operation in flight
when Kill is called, the overlapped structure that is part of the request
is deleted immediately, so when it actually completes it will not be valid
anymore.
Even if FileInputStream calls CancelIo, async_context_ has to be kept
around until the OS notifies that the operation was actually canceled, and
then the handle can be closed.
Issue attributes:
Status: Untriaged
Owner: [EMAIL PROTECTED]
Labels: Type-Bug Pri-1 OS-Windows Area-BrowserBackend
--
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
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
