Skip to content
This repository has been archived by the owner on Oct 23, 2019. It is now read-only.

High CPU usage when exporting #112

Open
maiqueg opened this issue Mar 14, 2019 · 4 comments
Open

High CPU usage when exporting #112

maiqueg opened this issue Mar 14, 2019 · 4 comments

Comments

@maiqueg
Copy link

maiqueg commented Mar 14, 2019

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?

@Lonami
Copy link
Collaborator

Lonami commented Mar 14, 2019

I don't think the bug is present in the version TE uses.

Using latest Python is always a good idea anyway.

Yes, of course TE should use latest Telethon some day.

@maiqueg
Copy link
Author

maiqueg commented Mar 14, 2019

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.

@Lonami
Copy link
Collaborator

Lonami commented Mar 14, 2019

It would be helpful if we could spot where exactly is getting stuck to hit 100% CPU usage, but right now I don't know how we could find that out.

@ghost
Copy link

ghost commented Mar 16, 2019

I have also experienced this using a Debian 9 VM in Windows.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants