mirror of
https://github.com/nodejs/node.git
synced 2025-05-08 11:21:41 +00:00
2ea2000625
Execute JS code in worker through same vm context while exiting from the main thread at arbitrary execution points, and make sure that the workers quiesce without crashing. `worker_threads` are not necessarily the subject of testing, those are used for easy simulation of multi-thread scenarios. Refs: https://github.com/nodejs/node/issues/25007 PR-URL: https://github.com/nodejs/node/pull/25085 Reviewed-By: Anna Henningsen <anna@addaleax.net>
22 lines
761 B
JavaScript
22 lines
761 B
JavaScript
'use strict';
|
|
const common = require('../common');
|
|
|
|
// Harden the thread interactions on the exit path.
|
|
// Ensure workers are able to bail out safe at
|
|
// arbitrary execution points. By running a lot of
|
|
// JS code in a tight loop, the expectation
|
|
// is that those will be at various control flow points
|
|
// preferrably in the JS land.
|
|
|
|
const { Worker } = require('worker_threads');
|
|
const code = 'setInterval(() => {' +
|
|
"require('v8').deserialize(require('v8').serialize({ foo: 'bar' }));" +
|
|
"require('vm').runInThisContext('x = \"foo\";');" +
|
|
"eval('const y = \"vm\";');}, 10);";
|
|
for (let i = 0; i < 9; i++) {
|
|
new Worker(code, { eval: true });
|
|
}
|
|
new Worker(code, { eval: true }).on('online', common.mustCall((msg) => {
|
|
process.exit(0);
|
|
}));
|