Updates:
Status: Fixed
Owner: [email protected]
Comment #2 on issue 27483 by [email protected]: Empty Chrome Frame
directories aren't removed even after restart
http://code.google.com/p/chromium/issues/detail?id=27483
Fixed, mostly. At least as fixed as I can make it without much plumbing.
The correct directories are now all scheduled for deletion and I have not
seen a case
where the files in Program Files don't get removed.
For the user profile directory, this MAY still occasionally fail if CF is
in use.
Here's why: the mechanism we use to schedule files for deletion is to call
out to
MoveFileEx asking it to delete files on reboot. MoveFileEx will only cause
files and
_empty_ directories to be deleted on reboot, so we traverse the tree of the
user
profile depth-first and delete each individual file before it's parent
directory.
If new files are created in the user profile between the time we uninstall
and the
time Chrome Frame is shut down / the machine is rebooted then not all of
the user
profile directories will be empty (since the new file couldn't be scheduled
to be
deleted before it existed). The session manager will then stop deleting
stuff and may
leave some directories behind. Fixing this will take quite a bit of work.
So for now, I will mark this as fixed as the delete-on-reboot mechanism
tries its
best and will get rid of the profile directory at least some of the time.
--
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
