diff options
author | haven@chromium.org <haven@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-05-07 13:18:55 +0000 |
---|---|---|
committer | haven@chromium.org <haven@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-05-07 13:18:55 +0000 |
commit | 01fe23ce00083502601f24a37e2dbc0696900d82 (patch) | |
tree | 04780407e8505d8f422a84569b12a36e49e340bd /chrome/browser/chromeos/input_method/input_method_engine_browsertests.cc | |
parent | bb2d615ad4ebea9c95d9211c21d6644cd0384f58 (diff) | |
download | chromium_src-01fe23ce00083502601f24a37e2dbc0696900d82.zip chromium_src-01fe23ce00083502601f24a37e2dbc0696900d82.tar.gz chromium_src-01fe23ce00083502601f24a37e2dbc0696900d82.tar.bz2 |
Updates handling of handlers in the image writer.
The Image Writer ran into some errors where Windows has been updating
the partition table of the disk between the writing and verification
stages. The key to preventing this seems to be to hold the handles open
between the two stages.
This changes the utility-process portion of the image writer to hold
open handles until closed or the file paths change. This means that a
write-and-verify operation on the same files will keep the file handles
open.
Initially the idea was to dismount the volumes to discourage windows
from writing, and this is something we wanted to add anyway, so this
adds that as well.
Note that the dismounting is called from the image_writer_handler so
that the write and verify methods remain unit-testable on fake files.
BUG=352442
Review URL: https://codereview.chromium.org/253543003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268719 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/chromeos/input_method/input_method_engine_browsertests.cc')
0 files changed, 0 insertions, 0 deletions