mirror of
https://github.com/nodejs/node.git
synced 2024-11-22 07:37:56 +01:00
873e5ce54a
PR-URL: https://github.com/nodejs/node/pull/46610 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Moshe Atlow <moshe@atlow.co.il> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
34 lines
1.1 KiB
JavaScript
34 lines
1.1 KiB
JavaScript
'use strict';
|
|
require('../common');
|
|
const vm = require('vm');
|
|
|
|
// We're testing a race condition so we just have to spin this in a loop
|
|
// for a little while and see if it breaks. The condition being tested
|
|
// is an `isolate->TerminateExecution()` reaching the main JS stack from
|
|
// the timeout watchdog.
|
|
const sandbox = { timeout: 5 };
|
|
const context = vm.createContext(sandbox);
|
|
const script = new vm.Script(
|
|
'var d = Date.now() + timeout;while (d > Date.now());',
|
|
);
|
|
const immediate = setImmediate(function() {
|
|
throw new Error('Detected vm race condition!');
|
|
});
|
|
|
|
// When this condition was first discovered this test would fail in 50ms
|
|
// or so. A better, but still incorrect implementation would fail after
|
|
// 100 seconds or so. If you're messing with vm timeouts you might
|
|
// consider increasing this timeout to hammer out races.
|
|
const giveUp = Date.now() + 5000;
|
|
do {
|
|
// The loop adjusts the timeout up or down trying to hit the race
|
|
try {
|
|
script.runInContext(context, { timeout: 5 });
|
|
++sandbox.timeout;
|
|
} catch {
|
|
--sandbox.timeout;
|
|
}
|
|
} while (Date.now() < giveUp);
|
|
|
|
clearImmediate(immediate);
|