From 4f13824bc9ae16232c3a68c1fc31edc40335214e Mon Sep 17 00:00:00 2001 From: "trop[bot]" <37223003+trop[bot]@users.noreply.github.com> Date: Thu, 31 Oct 2024 11:30:24 +0100 Subject: [PATCH] perf: remove isolate scope from DidProcessTask() (#44473) Co-authored-by: trop[bot] <37223003+trop[bot]@users.noreply.github.com> Co-authored-by: Charles Kerr --- shell/browser/microtasks_runner.cc | 1 - 1 file changed, 1 deletion(-) diff --git a/shell/browser/microtasks_runner.cc b/shell/browser/microtasks_runner.cc index ac8774e71053..e50ef5f610fd 100755 --- a/shell/browser/microtasks_runner.cc +++ b/shell/browser/microtasks_runner.cc @@ -17,7 +17,6 @@ void MicrotasksRunner::WillProcessTask(const base::PendingTask& pending_task, bool was_blocked_or_low_priority) {} void MicrotasksRunner::DidProcessTask(const base::PendingTask& pending_task) { - v8::Isolate::Scope scope(isolate_); // In the browser process we follow Node.js microtask policy of kExplicit // and let the MicrotaskRunner which is a task observer for chromium UI thread // scheduler run the microtask checkpoint. This worked fine because Node.js