1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-21 15:04:11 -05:00
denoland-deno/tests/node_compat/test/parallel/test-timers-same-timeout-wrong-list-deleted.js
Asher Gomez 29085895c9
chore: move tools/node_compat to tests/node_compat/runner (#23025)
The `tools/node_compat/node` submodule has been moved to
`tests/node_compat/runner/suite` and the remaining files within
`tools/node_compat` to `tests/node_compat/runner`.

Most of the changes are of the header within `tests/node_compat/test`
files. The `setup` and `test` tasks within `tests/node_comapt` execute
successfully.

Towards #22525
CC @mmastrac
2024-04-03 09:24:55 +11:00

41 lines
1.6 KiB
JavaScript

// deno-fmt-ignore-file
// deno-lint-ignore-file
// Copyright Joyent and Node contributors. All rights reserved. MIT license.
// Taken from Node 18.12.1
// This file is automatically generated by `tests/node_compat/runner/setup.ts`. Do not modify this file manually.
'use strict';
// This is a regression test for https://github.com/nodejs/node/issues/7722.
//
// When nested timers have the same timeout, calling clearTimeout on the
// older timer after it has fired causes the list the newer timer is in
// to be deleted. Since the newer timer was not cleared, it still blocks
// the event loop completing for the duration of its timeout, however, since
// no reference exists to it in its list, it cannot be canceled and its
// callback is not called when the timeout elapses.
const common = require('../common');
const TIMEOUT = common.platformTimeout(100);
const handle1 = setTimeout(common.mustCall(function() {
// Cause the old TIMEOUT list to be deleted
clearTimeout(handle1);
// Cause a new list with the same key (TIMEOUT) to be created for this timer
const handle2 = setTimeout(common.mustNotCall(), TIMEOUT);
setTimeout(common.mustCall(function() {
// Attempt to cancel the second timer. Fix for this bug will keep the
// newer timer from being dereferenced by keeping its list from being
// erroneously deleted. If we are able to cancel the timer successfully,
// the bug is fixed.
clearTimeout(handle2);
}), 1);
// When this callback completes, `listOnTimeout` should now look at the
// correct list and refrain from removing the new TIMEOUT list which
// contains the reference to the newer timer.
}), TIMEOUT);