Issue 2321: Acrobat holds handle to Chrome-> Application folder, even if the folder doesn't exist. http://code.google.com/p/chromium/issues/detail?id=2321
Comment #1 by [EMAIL PROTECTED]: Fixed in chrome revision 2287 This fixes http://code.google.com/p/chromium/issues/detail?id=2321, which was an issue with Adobe reader retaining an open handle to the chrome application folder causing issues with subsequent installs. This was because we did not specify the current directory in the ShellExecute call. This resulted in the chrome application folder becoming the current directory and hence the issue. Bug=2321 Issue attribute updates: Status: Fixed -- 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 -~----------~----~----~----~------~----~------~--~---
