GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — test: skip wasm allocation tests in workers · nodejs/node@7682e7e

File tree

Expand file treeCollapse file tree
Open diff view settings
Filter options
  • test/wasm-allocation
    • test-wasm-allocation-memory64.js
    • test-wasm-allocation.js
Expand file treeCollapse file tree
Open diff view settings
Collapse file

‎test/wasm-allocation/test-wasm-allocation-memory64.js‎

Copy file name to clipboardExpand all lines: test/wasm-allocation/test-wasm-allocation-memory64.js
+7-1Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,19 @@
44
// wasm memory64 with guard regions reserves 16GB of virtual address space.
55
'use strict';
66

7-
require('../common');
7+
const common = require('../common');
88
const assert = require('assert');
9+
const { isMainThread } = require('worker_threads');
910

1011
// The first allocation should succeed.
1112
const first = new WebAssembly.Memory({ address: 'i64', initial: 10n, maximum: 100n });
1213
assert(first);
1314

15+
if (!isMainThread) {
16+
// https://github.com/nodejs/node/issues/62870
17+
common.skip('Workers terminate instead of throwing');
18+
}
19+
1420
// Subsequent allocations should eventually fail due to running out of
1521
// virtual address space. memory64 reserves 16GB per allocation (vs 8GB for
1622
// memory32), so the limit is reached even faster.
Collapse file

‎test/wasm-allocation/test-wasm-allocation.js‎

Copy file name to clipboardExpand all lines: test/wasm-allocation/test-wasm-allocation.js
+21-2Lines changed: 21 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,5 +4,24 @@
44
// wasm memory32 with guard regions reserves 8GB of virtual address space.
55
'use strict';
66

7-
require('../common');
8-
new WebAssembly.Memory({ initial: 10, maximum: 100 });
7+
const common = require('../common');
8+
const assert = require('assert');
9+
const { isMainThread } = require('worker_threads');
10+
11+
// The first allocation should succeed.
12+
const first = new WebAssembly.Memory({ initial: 10, maximum: 100 });
13+
assert(first);
14+
15+
if (!isMainThread) {
16+
// https://github.com/nodejs/node/issues/62870
17+
common.skip('Workers terminate instead of throwing');
18+
}
19+
20+
// Subsequent allocations should eventually fail due to running out of
21+
// virtual address space.
22+
assert.throws(() => {
23+
const instances = [first];
24+
for (let i = 1; i < 30; i++) {
25+
instances.push(new WebAssembly.Memory({ initial: 10, maximum: 100 }));
26+
}
27+
}, /WebAssembly\.Memory/);

0 commit comments

Comments
0 (0)
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.