Kurigram stops receiving updates after a while

[EDM115]

Checklist

• I am sure the error is coming from Pyrogram's code and not elsewhere
• I have searched in the issue tracker for similar bug reports, including closed ones
• I ran pip3 install -U https://github.com/pyrogram/pyrogram/archive/master.zip and reproduced the issue using the latest development version

Description

Okay so I'm encountering this one since a while and it truly puzzles me.
I have a bot that processes multiple tasks regularly (download and uploads files mainly, much more than sending text messages anyway). And for whatever reason, after ~24h, it just stops receiving any updates from Telegram, just like if the connexion closed.
I tried to wait to see if it was a FloodWait, but no, and such thing wasn't on the logs (I'm used to see some FloodWaits but it doesn't seem to be the cause here).
It's not a network issue either, as if I restart the bot it works fine again for ~24h.

What's even crazier is that it only happens on heavy load. When the exact same code was used on a bot used by few peoples not even every day, on the same server, the bot could stay online for more than a month without any issue

Steps to reproduce

1. Create a bot that can download and upload files
2. Have it being used by hundred of people everyday spamming it
3. Observe that after ~24h the bot stops receiving updates without logging anything related to FloodWaits

Note

It can also happen on shorter amounts of time, depending on how much overused the bot gets

Code example

the code used can be found at https://github.com/EDM115/unzip-bot/tree/129fda86c28fad7c42f71c05e17813878c610600, but it's more the usage of the bot than the code that matters as it seems

Logs

Kurigram just stops logging anything when it stops receiving the updates

[zawsq]

This issue is irrelevant, doesn't provide a proper reasonings. In some case a function of your bot is maybe blocking pyrogram async coroutine.

[Mehdioop]

same issue

[EDM115]

there was a very useful comment here that has sadly been deleted by its owner :(