15272bdcce
If multiple isolates are running concurrently and one of them calls `quit`, we should not delete the counters map, because another isolate might still access it. R=mlippautz@chromium.org CC=nikolaos@chromium.org Bug: v8:12453 Change-Id: I6d41478f188f0043b7d6055b0872574c28fd3039 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3310807 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#78226}
19 lines
633 B
JavaScript
19 lines
633 B
JavaScript
// Copyright 2021 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: --dump-counters
|
|
|
|
d8.file.execute('test/mjsunit/wasm/wasm-module-builder.js');
|
|
|
|
// Test that if two isolates are running (with the --isolates flag on the test
|
|
// runner) and one of them calls `quit`, the other one can still write to
|
|
// counters concurrently.
|
|
|
|
if (typeof WebAssembly !== 'undefined') { // Skip on jitless.
|
|
const builder = new WasmModuleBuilder();
|
|
builder.addFunction('f', kSig_v_v).addBody([]);
|
|
builder.asyncInstantiate();
|
|
}
|
|
quit();
|