test: add validation for listener removal in read streams

[Paraspandey-debugs]

Add a regression test covering the listener leak reported in #64214,
where repeated fileHandle.createReadStream({ autoClose: false, ... })
calls each attach a 'close' listener to the FileHandle that is never
removed once the stream ends. Over many ranged reads on a long-lived
handle this triggers MaxListenersExceededWarning and leaks memory.

The test creates 100 short-lived ranged read streams from a single
FileHandle and asserts that the FileHandle's 'close' listener count
returns to its pre-loop baseline after each stream is fully consumed.

A previous fix (#64227) was merged and then reverted (#65387) after
introducing a separate issue where a stream's reference on the
FileHandle could be released more than once. This PR adds test
coverage for the originally reported listener leak only.

Refs: #64214
Refs: #64227
Refs: #65387

[Paraspandey-debugs]

Add a regression test covering the listener leak reported in #64214,
where repeated fileHandle.createReadStream({ autoClose: false, ... })
calls each attach a 'close' listener to the FileHandle that is never
removed once the stream ends. Over many ranged reads on a long-lived
handle this triggers MaxListenersExceededWarning and leaks memory.

The test creates 100 short-lived ranged read streams from a single
FileHandle and asserts that the FileHandle's 'close' listener count
returns to its pre-loop baseline after each stream is fully consumed.

A previous fix (#64227) was merged and then reverted (#65387) after
introducing a separate issue where a stream's reference on the
FileHandle could be released more than once. This PR adds test
coverage for the originally reported listener leak only.

Refs: #64214
Refs: #64227
Refs: #65387

[Paraspandey-debugs]

Add a regression test covering the listener leak reported in #64214,
where repeated fileHandle.createReadStream({ autoClose: false, ... })
calls each attach a 'close' listener to the FileHandle that is never
removed once the stream ends. Over many ranged reads on a long-lived
handle this triggers MaxListenersExceededWarning and leaks memory.

The test creates 100 short-lived ranged read streams from a single
FileHandle and asserts that the FileHandle's 'close' listener count
returns to its pre-loop baseline after each stream is fully consumed.

A previous fix (#64227) was merged and then reverted (#65387) after
introducing a separate issue where a stream's reference on the
FileHandle could be released more than once. This PR adds test
coverage for the originally reported listener leak only.

Refs: #64214
Refs: #64227
Refs: #65387

[Paraspandey-debugs]

Add a regression test covering the listener leak reported in #64214,
where repeated fileHandle.createReadStream({ autoClose: false, ... })
calls each attach a 'close' listener to the FileHandle that is never
removed once the stream ends. Over many ranged reads on a long-lived
handle this triggers MaxListenersExceededWarning and leaks memory.

The test creates 100 short-lived ranged read streams from a single
FileHandle and asserts that the FileHandle's 'close' listener count
returns to its pre-loop baseline after each stream is fully consumed.

A previous fix (#64227) was merged and then reverted (#65387) after
introducing a separate issue where a stream's reference on the
FileHandle could be released more than once. This PR adds test
coverage for the originally reported listener leak only.

Refs: #64214
Refs: #64227
Refs: #65387

[Paraspandey-debugs]

Add a regression test covering the listener leak reported in #64214,
where repeated fileHandle.createReadStream({ autoClose: false, ... })
calls each attach a 'close' listener to the FileHandle that is never
removed once the stream ends. Over many ranged reads on a long-lived
handle this triggers MaxListenersExceededWarning and leaks memory.

The test creates 100 short-lived ranged read streams from a single
FileHandle and asserts that the FileHandle's 'close' listener count
returns to its pre-loop baseline after each stream is fully consumed.

A previous fix (#64227) was merged and then reverted (#65387) after
introducing a separate issue where a stream's reference on the
FileHandle could be released more than once. This PR adds test
coverage for the originally reported listener leak only.

Refs: #64214
Refs: #64227
Refs: #65387

[Paraspandey-debugs]

Add a regression test covering the listener leak reported in #64214,
where repeated fileHandle.createReadStream({ autoClose: false, ... })
calls each attach a 'close' listener to the FileHandle that is never
removed once the stream ends. Over many ranged reads on a long-lived
handle this triggers MaxListenersExceededWarning and leaks memory.

The test creates 100 short-lived ranged read streams from a single
FileHandle and asserts that the FileHandle's 'close' listener count
returns to its pre-loop baseline after each stream is fully consumed.

A previous fix (#64227) was merged and then reverted (#65387) after
introducing a separate issue where a stream's reference on the
FileHandle could be released more than once. This PR adds test
coverage for the originally reported listener leak only.

Refs: #64214
Refs: #64227
Refs: #65387

[Paraspandey-debugs]

Add a regression test covering the listener leak reported in #64214,
where repeated fileHandle.createReadStream({ autoClose: false, ... })
calls each attach a 'close' listener to the FileHandle that is never
removed once the stream ends. Over many ranged reads on a long-lived
handle this triggers MaxListenersExceededWarning and leaks memory.

The test creates 100 short-lived ranged read streams from a single
FileHandle and asserts that the FileHandle's 'close' listener count
returns to its pre-loop baseline after each stream is fully consumed.

A previous fix (#64227) was merged and then reverted (#65387) after
introducing a separate issue where a stream's reference on the
FileHandle could be released more than once. This PR adds test
coverage for the originally reported listener leak only.

Refs: #64214
Refs: #64227
Refs: #65387

[Paraspandey-debugs]

Add a regression test covering the listener leak reported in #64214,
where repeated fileHandle.createReadStream({ autoClose: false, ... })
calls each attach a 'close' listener to the FileHandle that is never
removed once the stream ends. Over many ranged reads on a long-lived
handle this triggers MaxListenersExceededWarning and leaks memory.

The test creates 100 short-lived ranged read streams from a single
FileHandle and asserts that the FileHandle's 'close' listener count
returns to its pre-loop baseline after each stream is fully consumed.

A previous fix (#64227) was merged and then reverted (#65387) after
introducing a separate issue where a stream's reference on the
FileHandle could be released more than once. This PR adds test
coverage for the originally reported listener leak only.

Refs: #64214
Refs: #64227
Refs: #65387