diff options
| author | ssid <ssid@chromium.org> | 2016-02-01 08:09:51 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-02-01 16:10:48 +0000 |
| commit | 2bf18cfdfa1b8b0bd829edea2d90277e7e5b0b71 (patch) | |
| tree | dbe0139caea9291fb64132f07c20fb7d9bfefc4e /base | |
| parent | 89b4a2addd0e3e82a1ca8213d31323fdc2e6395a (diff) | |
| download | chromium_src-2bf18cfdfa1b8b0bd829edea2d90277e7e5b0b71.zip chromium_src-2bf18cfdfa1b8b0bd829edea2d90277e7e5b0b71.tar.gz chromium_src-2bf18cfdfa1b8b0bd829edea2d90277e7e5b0b71.tar.bz2 | |
Remove --no-sandbox flag from command line for telemetry
Now that the browser is able to dump for child processes the
--no-sandbox flag is not required for getting memory statistics. So,
this is removed form the telemetry benchmarks.
BUG=461788
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:win_perf_bisect
Review URL: https://codereview.chromium.org/1584583003
Cr-Commit-Position: refs/heads/master@{#372667}
Diffstat (limited to 'base')
| -rw-r--r-- | base/trace_event/memory_dump_manager.cc | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/base/trace_event/memory_dump_manager.cc b/base/trace_event/memory_dump_manager.cc index a0f0af3..cb59448 100644 --- a/base/trace_event/memory_dump_manager.cc +++ b/base/trace_event/memory_dump_manager.cc @@ -419,9 +419,7 @@ void MemoryDumpManager::ContinueAsyncProcessDump( if (!mdpinfo->disabled) { if (mdpinfo->consecutive_failures >= kMaxConsecutiveFailuresCount) { mdpinfo->disabled = true; - disabled_reason = - "Dump failure, possibly related with sandboxing (crbug.com/461788)." - " Try --no-sandbox."; + disabled_reason = "Dump failed multiple times consecutively."; } else if (post_task_failed && mdpinfo->task_runner) { // Don't disable unbound dump providers. The utility thread is normally // shutdown when disabling the trace and getting here in this case is |