diff options
| author | Elijah Taylor <elijahtaylor@chromium.org> | 2014-09-26 10:56:15 -0700 |
|---|---|---|
| committer | Elijah Taylor <elijahtaylor@chromium.org> | 2014-09-26 17:56:44 +0000 |
| commit | 51533547c9450ea9aabc3f0e7ada54e5af2a7343 (patch) | |
| tree | 19c49dcf164ad9a7819674d94e850104368e5a1c /build/build_config.h | |
| parent | 05ff2b5aa91e7464fb06b3ceccabd81b84431277 (diff) | |
| download | chromium_src-51533547c9450ea9aabc3f0e7ada54e5af2a7343.zip chromium_src-51533547c9450ea9aabc3f0e7ada54e5af2a7343.tar.gz chromium_src-51533547c9450ea9aabc3f0e7ada54e5af2a7343.tar.bz2 | |
Check multi-crx path for force update based on manifest entries
The previous CL (https://codereview.chromium.org/540673002) was not fully
correct. It used a path based on <nacl_arch>, but the path can be arbitrary
based on entries in the extension's manifest.
If the extension used non-nacl_arch paths, it would continually download and
install the same copy of the extension, eventually filling up the user's disk if
left long enough without restarting Chrome.
BUG=414156
Review URL: https://codereview.chromium.org/596193002
Cr-Commit-Position: refs/heads/master@{#296514}
(cherry picked from commit 74cafd39701dd9b66ea219a2a4ef0c9d88d76eec)
Review URL: https://codereview.chromium.org/605303002
Cr-Commit-Position: refs/branch-heads/2125@{#499}
Cr-Branched-From: b68026d94bda36dd106a3d91a098719f952a9477-refs/heads/master@{#290040}
Diffstat (limited to 'build/build_config.h')
0 files changed, 0 insertions, 0 deletions