Sanitizer reports leak, even if count of pending ops before and after test is identical

[lucacasonato]

const listener = Deno.listen({ port: 8080 });

const conn1 = await Deno.connect({ port: 8080 });
const conn2 = await listener.accept();

(async () => {
  while (true) {
    await conn1.write(new TextEncoder().encode("Hello World"));
    await conn2.read(new Uint8Array(11));
  }
})();

Deno.test("hello world", async () => {
  await new Promise((resolve) => setTimeout(resolve, 1000));
});

In Deno 1.40.0 this works fine.

In Deno 1.41.2 this errors with:

running 1 test from ./test.ts
hello world ... FAILED (1s)

 ERRORS 

hello world => ./test.ts:13:6
error: Leaks detected:
  - An async call to op_read was started before the test, but completed during the test. Async operations should not complete in a test if they were not started in that test.
  - An async call to op_read was started in this test, but never completed.
To get more details where leaks occurred, run again with the --trace-leaks flag.

 FAILURES 

hello world => ./test.ts:13:6

FAILED | 0 passed | 1 failed (1s)

error: Test failed

The issue is that we were previously comparing the count of pending ops before and after the test (which in this example will be identical), but now we are comparing the actual ops completing or not. This means that a loop reading from a subprocess stdout (esbuild) in global scope, will cause leaks here, even though in reality nothing is leaking (the count of ongoing read operations is the same before and after the test).

Version: Deno 1.41.2

[dsherret]

Some glitch created two issues. Closing in favour of #22926