59136c6045
V8FileLogger has a dynamic behaviour when listening to code events, i.e., it can stop listening without removing itself from the Logger, which invalidates the field is_listening_to_code_events_. This field is only updated when adding/removing an event listener. This cache was recently introduced in a refactoring https://crrev.com/c/3582125 Bug: chromium:1400809 Change-Id: If93c88a6a64f5bf2c10265ac1db455ea498733a0 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4136726 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Patrick Thier <pthier@chromium.org> Reviewed-by: Patrick Thier <pthier@chromium.org> Cr-Commit-Position: refs/heads/main@{#85113}
12 lines
288 B
JavaScript
12 lines
288 B
JavaScript
// Copyright 2022 the V8 project authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style license that can be
|
|
// found in the LICENSE file.
|
|
|
|
// Flags: --expose-gc --logfile='+' --log
|
|
|
|
const log = d8.log.getAndStop();
|
|
gc();
|
|
function __f_6() {
|
|
}
|
|
__v_1 = __f_6();
|