You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 23, 2019. It is now read-only.
Anyone else having really high CPU usage when executing telegram-export?
It reaches 100% with my Xeon quad 2.66ghz.
I saw a bug that was fixed on the new telethon version, that could be related:
"Some bug in Python 3.5.2’s asyncio causing 100% CPU load if you forgot to call client.disconnect(). The method is called for you on object destruction, but you still should disconnect manually or use a with block."
Any plans to upgrade the telegram-export to support telethon 1.6.2?
The text was updated successfully, but these errors were encountered:
I was running python 3.5.2, upgraded to 3.7.2 and still reaching 100% CPU when using TE. This is not normal, right? I could provide a few logs if you guide me on how/where to collect them.
Anyone else having really high CPU usage when executing telegram-export?
It reaches 100% with my Xeon quad 2.66ghz.
I saw a bug that was fixed on the new telethon version, that could be related:
"Some bug in Python 3.5.2’s asyncio causing 100% CPU load if you forgot to call client.disconnect(). The method is called for you on object destruction, but you still should disconnect manually or use a with block."
Any plans to upgrade the telegram-export to support telethon 1.6.2?
The text was updated successfully, but these errors were encountered: