forked from chromium/chromium
-
-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "[Extensions] Change install directory of .zip file installs."
This reverts commit 1a7cebd. Reason for revert: This causes unexpected .zip file deletion due to incorrect extension_garbage_collector.cc logic. See https://crbug.com/1378775#c12 for details. Original change's description: > [Extensions] Change install directory of .zip file installs. > > Change the install directory to "UnpackedExtensions" subdir of the > profile directory. > > I've put it behind a default enabled flag to give us the later option of > an emergency rollback due to the complexity of the change and the fact > that the change modifies files. > > Before this change we installed .zip file installed extensions to a > unique subdir of base::DIR_TEMP. This could cause confusion when the > temporary directory used for installation would be deleted by the OS > (e.g. /tmp on Linux, `NSTemporaryDirectory` on Mac, and etc.) which are > commonly cleared on varied timelines). This caused issues like the html > file for a badge popup failing to be found at runtime and the extension > disappearing from chromium on restart when it no longer could find the > directory. > > After this change we install them to a non-temporary > "UnpackedExtensions" subdir of the profile dir (at the same level as the > "Extensions" dir where we install packed .crx and webstore installs). > > This allows the extension to persist until the user chooses to uninstall > the (from .zip) extension. > > I kept the original install folder format of (example good.zip) > ../<profile_dir>/UnpackedExtensions/good_XXXXXX/ where the Xs are a > unique combination (for that folder) of alphanumeric characters but that > was to be consistent more than anything else. > > Extra work had to be done with extension_garbage_collector.cc to ensure > that if the directory deletion failed it would eventually come around > and delete/cleanup the directory so it doesn't linger (because there > is now a new install location). > > This does not cause the Extension to be synced. > > Low-Coverage-Reason: extension_garbage_collector.cc we don't seem to > cover NOTREACHED() in unit tests. > > Bug: 1378775 > Change-Id: If793f363ec76bf6c36c7a77f8ebd8c6ad8c8e1d5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4313024 > Auto-Submit: Justin Lulejian <jlulejian@chromium.org> > Reviewed-by: David Bertoni <dbertoni@chromium.org> > Commit-Queue: Justin Lulejian <jlulejian@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1124983} (cherry picked from commit f341451) Bug: 1378775 Change-Id: Ic60fb1694375b5eb302d2f6498f04ddd691acd26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4477804 Reviewed-by: David Bertoni <dbertoni@chromium.org> Commit-Queue: Justin Lulejian <jlulejian@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1136022} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4481330 Auto-Submit: Justin Lulejian <jlulejian@chromium.org> Commit-Queue: David Bertoni <dbertoni@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5735@{#9} Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
- Loading branch information
Justin Lulejian
authored and
Chromium LUCI CQ
committed
Apr 26, 2023
1 parent
1d44ee1
commit 46d9268
Showing
25 changed files
with
237 additions
and
922 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.