v8: Remove trace event category warming
Since all categories are now statically defined, there's no need to warm any of them up explicitly in order for the categories to show up in the tracing UI. Depends on https://chromium-review.googlesource.com/c/chromium/src/+/1401273. Bug: chromium:914579 Change-Id: I8ae8977130ae89d6ee3351194ad258d13f3c14f4 Reviewed-on: https://chromium-review.googlesource.com/c/1402779 Reviewed-by: Alexei Filippov <alph@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Sami Kyöstilä <skyostil@chromium.org> Cr-Commit-Position: refs/heads/master@{#58699}
This commit is contained in:
parent
81a36c77ed
commit
298fb68368
@ -13,10 +13,6 @@ namespace internal {
|
||||
|
||||
TracingCpuProfilerImpl::TracingCpuProfilerImpl(Isolate* isolate)
|
||||
: isolate_(isolate), profiling_enabled_(false) {
|
||||
// Make sure tracing system notices profiler categories.
|
||||
TRACE_EVENT_WARMUP_CATEGORY(TRACE_DISABLED_BY_DEFAULT("v8.cpu_profiler"));
|
||||
TRACE_EVENT_WARMUP_CATEGORY(
|
||||
TRACE_DISABLED_BY_DEFAULT("v8.cpu_profiler.hires"));
|
||||
V8::GetCurrentPlatform()->GetTracingController()->AddTraceStateObserver(this);
|
||||
}
|
||||
|
||||
|
@ -19,11 +19,6 @@ void TracingCategoryObserver::SetUp() {
|
||||
v8::internal::V8::GetCurrentPlatform()
|
||||
->GetTracingController()
|
||||
->AddTraceStateObserver(TracingCategoryObserver::instance_);
|
||||
TRACE_EVENT_WARMUP_CATEGORY(TRACE_DISABLED_BY_DEFAULT("v8.runtime_stats"));
|
||||
TRACE_EVENT_WARMUP_CATEGORY(
|
||||
TRACE_DISABLED_BY_DEFAULT("v8.runtime_stats_sampling"));
|
||||
TRACE_EVENT_WARMUP_CATEGORY(TRACE_DISABLED_BY_DEFAULT("v8.gc_stats"));
|
||||
TRACE_EVENT_WARMUP_CATEGORY(TRACE_DISABLED_BY_DEFAULT("v8.ic_stats"));
|
||||
}
|
||||
|
||||
void TracingCategoryObserver::TearDown() {
|
||||
|
Loading…
Reference in New Issue
Block a user