From 0da5c656b48ed03d5405f5b2c862ba52faec64f2 Mon Sep 17 00:00:00 2001 From: Joyee Cheung Date: Tue, 4 Apr 2023 05:19:02 +0200 Subject: [PATCH] test: move test-shadow-realm-gc.js to known_issues There is actually a leak. The test doesn't exercise the right path to create a substantial enough object graph (e.g. accessing something that results in the loading of a binding). This does something more complicated in the test and moves it to known_issues until we find a fix. PR-URL: https://github.com/nodejs/node/pull/47355 Refs: https://github.com/nodejs/node/issues/47353 Reviewed-By: Colin Ihrig Reviewed-By: Chengzhong Wu Reviewed-By: Yagiz Nizipli --- test/known_issues/known_issues.status | 3 +++ test/known_issues/test-shadow-realm-gc.js | 13 +++++++++++++ 2 files changed, 16 insertions(+) create mode 100644 test/known_issues/test-shadow-realm-gc.js diff --git a/test/known_issues/known_issues.status b/test/known_issues/known_issues.status index 7a50c10404c723..e19a87e7c39b6c 100644 --- a/test/known_issues/known_issues.status +++ b/test/known_issues/known_issues.status @@ -11,6 +11,9 @@ prefix known_issues # foreseeable future. The test itself is flaky and skipped. It # serves as a demonstration of the issue only. test-vm-timeout-escape-queuemicrotask: SKIP +# Skipping it because it crashes out of OOM instead of exiting. +# https://github.com/nodejs/node/issues/47353 +test-shadow-realm-gc: SKIP [$system==win32] diff --git a/test/known_issues/test-shadow-realm-gc.js b/test/known_issues/test-shadow-realm-gc.js new file mode 100644 index 00000000000000..cf15324e5cec06 --- /dev/null +++ b/test/known_issues/test-shadow-realm-gc.js @@ -0,0 +1,13 @@ +// Flags: --experimental-shadow-realm --max-old-space-size=20 +'use strict'; + +/** + * Verifying ShadowRealm instances can be correctly garbage collected. + */ + +require('../common'); + +for (let i = 0; i < 1000; i++) { + const realm = new ShadowRealm(); + realm.evaluate('new TextEncoder(); 1;'); +}