Chromium Code Reviews| Index: content/renderer/devtools/v8_sampling_profiler.cc |
| diff --git a/content/renderer/devtools/v8_sampling_profiler.cc b/content/renderer/devtools/v8_sampling_profiler.cc |
| index cdad93b20063b65d286b637f5911fe185965bd60..ddbc28e53f307298cd21baadbdc67719319b7ce8 100644 |
| --- a/content/renderer/devtools/v8_sampling_profiler.cc |
| +++ b/content/renderer/devtools/v8_sampling_profiler.cc |
| @@ -327,23 +327,23 @@ void Sampler::HandleJitCodeEvent(const v8::JitCodeEvent* event) { |
| return; |
| switch (event->type) { |
| case v8::JitCodeEvent::CODE_ADDED: |
| - TRACE_EVENT_INSTANT1(TRACE_DISABLED_BY_DEFAULT("v8.cpu_profile"), |
| - "JitCodeAdded", TRACE_EVENT_SCOPE_THREAD, "data", |
| - JitCodeEventToTraceFormat(event)); |
| + TRACE_EVENT_METADATA1(TRACE_DISABLED_BY_DEFAULT("v8.cpu_profile"), |
| + "JitCodeAdded", TRACE_EVENT_SCOPE_THREAD, "data", |
|
dsinclair
2015/06/30 18:14:17
What does SCOPE_THREAD mean for a metadata event?
alph
2015/07/01 12:28:08
Not really needed, but I thought it might be usefu
|
| + JitCodeEventToTraceFormat(event)); |
| base::subtle::NoBarrier_AtomicIncrement( |
| &sampler->code_added_events_count_, 1); |
| break; |
| case v8::JitCodeEvent::CODE_MOVED: |
| - TRACE_EVENT_INSTANT1(TRACE_DISABLED_BY_DEFAULT("v8.cpu_profile"), |
| - "JitCodeMoved", TRACE_EVENT_SCOPE_THREAD, "data", |
| - JitCodeEventToTraceFormat(event)); |
| + TRACE_EVENT_METADATA1(TRACE_DISABLED_BY_DEFAULT("v8.cpu_profile"), |
| + "JitCodeMoved", TRACE_EVENT_SCOPE_THREAD, "data", |
| + JitCodeEventToTraceFormat(event)); |
| break; |
| case v8::JitCodeEvent::CODE_REMOVED: |
| - TRACE_EVENT_INSTANT1(TRACE_DISABLED_BY_DEFAULT("v8.cpu_profile"), |
| - "JitCodeRemoved", TRACE_EVENT_SCOPE_THREAD, "data", |
| - JitCodeEventToTraceFormat(event)); |
| + TRACE_EVENT_METADATA1(TRACE_DISABLED_BY_DEFAULT("v8.cpu_profile"), |
| + "JitCodeRemoved", TRACE_EVENT_SCOPE_THREAD, "data", |
| + JitCodeEventToTraceFormat(event)); |
| break; |
| case v8::JitCodeEvent::CODE_ADD_LINE_POS_INFO: |