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

Issue 617208 link

Starred by 1 user

Issue metadata

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

Blocking:
issue 613198



Sign in to add a comment

MemoryInfra: Trace config should have information about allowed dump types

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

Issue description

Background context:go/memory-infra: memory profiling in chrome://tracing

For background tracing mode any components can request a global dump with heavy mode and we might end up uploading unexpected data in field trials.
To fix this the trace config should be able to tell memory-infra that only specific dump modes are allowed for the tracing session. 
On the other hand trace config can also include a set of category names that are allowed to trigger a dump like "v8, blinkgc", etc..
 

Comment 1 by ssid@chromium.org, Jun 3 2016

Labels: -Pri-2 Pri-3
Project Member

Comment 2 by bugdroid1@chromium.org, Jun 22 2016

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

commit 40638de0bd1dbd66662c09b95bdd1df09ab9258c
Author: ssid <ssid@chromium.org>
Date: Wed Jun 22 19:40:31 2016

[tracing] Introduce "allowed_dump_modes" for memory dump config

The "allowed_dump_modes" contains a list of dump modes that are allowed
for memory dumps in the current session. This is to prevent any other
components from triggering explicit dumps with unexpected details. Trace
config now controls the modes allowed. If not mentioned then by default
all the modes are allowed.

BUG= 617208 
TBR=oysteine@chromium.org

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

[modify] https://crrev.com/40638de0bd1dbd66662c09b95bdd1df09ab9258c/base/trace_event/memory_dump_manager.cc
[modify] https://crrev.com/40638de0bd1dbd66662c09b95bdd1df09ab9258c/base/trace_event/memory_dump_manager.h
[modify] https://crrev.com/40638de0bd1dbd66662c09b95bdd1df09ab9258c/base/trace_event/memory_dump_manager_unittest.cc
[modify] https://crrev.com/40638de0bd1dbd66662c09b95bdd1df09ab9258c/base/trace_event/memory_dump_request_args.h
[modify] https://crrev.com/40638de0bd1dbd66662c09b95bdd1df09ab9258c/base/trace_event/trace_config.cc
[modify] https://crrev.com/40638de0bd1dbd66662c09b95bdd1df09ab9258c/base/trace_event/trace_config.h
[modify] https://crrev.com/40638de0bd1dbd66662c09b95bdd1df09ab9258c/base/trace_event/trace_config_memory_test_util.h
[modify] https://crrev.com/40638de0bd1dbd66662c09b95bdd1df09ab9258c/base/trace_event/trace_config_unittest.cc
[modify] https://crrev.com/40638de0bd1dbd66662c09b95bdd1df09ab9258c/content/browser/devtools/protocol/tracing_handler_unittest.cc
[modify] https://crrev.com/40638de0bd1dbd66662c09b95bdd1df09ab9258c/content/browser/tracing/background_tracing_manager_impl.cc

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

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

Sign in to add a comment