New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 622047 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 613198



Sign in to add a comment

Crash uploader uploads large file over mobile data for field trials

Project Member Reported by ssid@chromium.org, Jun 21 2016

Issue description

For background tracing field trials, we do not want to upload large trace files over mobile data, especially in cases where the user is not aware of this being turned on. The current trace size limit is 10MB, this should be reduced to 100KB if we are using data.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Jun 23 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f7de02da8220c2d43301d41ee232002e79d87218

commit f7de02da8220c2d43301d41ee232002e79d87218
Author: ssid <ssid@chromium.org>
Date: Thu Jun 23 17:29:17 2016

Limit the background trials upload size to 100Kib when using mobile data

The crash data is uploaded only if the file size was less than 10MB.
But, this does not consider if device is running on wifi or mobile data.
Uploading 10Mib crash files over data will be undesireable for android
and ios users. To fix this issue, the limit is set to 100Kib if the
connection is over data or connection type is unknown when tracing is
running for background field trials.

BUG= 622047 

Review-Url: https://codereview.chromium.org/2085623005
Cr-Commit-Position: refs/heads/master@{#401644}

[modify] https://crrev.com/f7de02da8220c2d43301d41ee232002e79d87218/chrome/browser/tracing/background_tracing_field_trial.cc
[modify] https://crrev.com/f7de02da8220c2d43301d41ee232002e79d87218/chrome/browser/tracing/crash_service_uploader.cc
[modify] https://crrev.com/f7de02da8220c2d43301d41ee232002e79d87218/chrome/browser/tracing/crash_service_uploader.h

Comment 2 by ssid@chromium.org, Jun 23 2016

Status: Fixed (was: Untriaged)
Components: Internals>Instrumentation>Memory

Sign in to add a comment