Dmitry Erlikh

@webknjaz may be we could add a debug level logging to `feed_data()` method to make debugging of such issues easier in the future?

> The only thing we can do is the conversion of exception with the attached stacktrace into a logged warning. @asvetlov can you add more details what exactly should happen...

Just did a check on my machine on 2a9d5e9e (master): ``` Filename: ./tests/4833_test.py Line # Mem usage Increment Occurences Line Contents ============================================================ 22 32.4 MiB 32.4 MiB 1 @profile 23...

Same PC on aiohttp 3.7.2 ``` Line # Mem usage Increment Occurences Line Contents ============================================================ 22 26.7 MiB 26.7 MiB 1 @profile 23 async def quicktest(): 24 26.7 MiB 0.0...

@asvetlov in my environment it is not needed. In the `main` function there is no memory leak. May be it was a problem in older Python 3.8 or may be...

For CentOS I've got the leak :-( ``` Line # Mem usage Increment Occurences Line Contents ============================================================ 22 28.3 MiB 28.3 MiB 1 @profile 23 async def quicktest(): 24 28.3...

There is an issue in `aiohttp` for it. https://github.com/aio-libs/aiohttp/issues/5366

Looks like test_iter was added in e87033c

Looks like this link problem came from OpenSSL version update (3.2.0 ->3.2.1) in Chocolatey

This issue can be closed. Now Windows build is green.