diff options
| author | Alex Deymo <deymo@chromium.org> | 2015-07-17 18:56:37 -0700 |
|---|---|---|
| committer | ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> | 2015-07-23 09:59:35 +0000 |
| commit | cfe8c15afc6c725a9626577db6504675310498d8 (patch) | |
| tree | 043b8f708c3815691cd06c3aeb5cd09923e518f7 /payload_generator/blob_file_writer_unittest.cc | |
| parent | 2d3b2d635e50c6886e285afb86c3187d9e0bd360 (diff) | |
update_engine: Set a sane chunk_size default.
When generating deltas of normal ChromeOS images, the expected maximum
size of a file is about 120 MiB, which is reasonble to handle in
memory during payload generation and application. Nevertheless, if we
find a very big file (or pseudo-file) we could easilly run out of
memory when trying to produce a BSDIFF for it. This patch limits
the chunk_size to 200 MiB, which should not impact any normal
ChromeOS payload.
BUG=chromium:485397
TEST=cros_generate_update_payload produces the same payload.
Change-Id: I1c43e619f424253cab20f0d384c7e90d10bd707d
Reviewed-on: https://chromium-review.googlesource.com/286535
Reviewed-by: Gilad Arnold <garnold@chromium.org>
Tested-by: Alex Deymo <deymo@chromium.org>
Trybot-Ready: Alex Deymo <deymo@chromium.org>
Commit-Queue: Alex Deymo <deymo@chromium.org>
Diffstat (limited to 'payload_generator/blob_file_writer_unittest.cc')
0 files changed, 0 insertions, 0 deletions