Evgeny Nizhibitsky added the comment:
Oh, I see that in the initial code with leakage (it was heavy
ThreadPoolExecutor + xgboost thing) there was an await but I must have lost it
somewhere while reducing it to the minimal example and finished in the wrong
direction.
Glad too see
New submission from Evgeny Nizhibitsky :
I have run into a memory leak caused by using run_in_executor +
ThreadPoolExecutor while running some stability tests with custom web services.
It was 1 MB leaked for 1k requests made for my case and I've extracted the root
cause and converted
