1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
// deno-fmt-ignore-file// deno-lint-ignore-file
// Copyright Joyent and Node contributors. All rights reserved. MIT license.// Taken from Node 18.12.0// This file is automatically generated by "node/_tools/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);