-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure in Telegram setup results in RAM leak #272
Comments
Hi @Lympri - thanks for reporting a bug! Could you share a bit more detailed steps, as I cannot reproduce the problem here. I tried from a clean slate, i.e. using a non-existent nchat config dir, selected Telegram, entered a valid phone number, entered wrong authentication code. Nchat exits directly (i.e. no hang or repeated log entries).
(I also attempted wrong phone number and wrong password, same results) Is the above what you did too (wrong authentication code), or something else? Do you have a single profile, or multiple protocols/profiles set up (like ok WhatsApp + failed Telegram, or other combination)? Thanks! |
I cannot login to telegram as it says that I need to update telegram. My telegram-cli should be at newest version
I am not quite sure, I had in profiles folder 2 directories, 1 for WhatsApp (working, but I didn't use it because using it ate all ram) |
I cannot login to telegram as it says that I need to update telegram. My telegram-cli should be at newest version
I am not quite sure, I had in profiles folder 2 directories, 1 for WhatsApp (working, but I didn't use it because using it ate all ram) and another for Telegram (but it's removed allready). After that removal WhatsApp has worked like a charm. |
Could you share the error message? The telegram service maintains support for old clients pretty long, so you would need a very old version of nchat to run into that, should definitely not happen in
nchat does not use telegram-cli. nchat has its telegram client code bundled / built-in.
Thanks, this is useful! I will try this scenario. |
Was able to reproduce repeated
Will prepare a fix which avoids the infinite loop in this scenario. I'm still not sure how one can end up in this situation (without manually editing/removing telegram.conf) but will do this fix for now. |
The high CPU usage and memory leak on broken Telegram setup should be addressed in above commit. Please let me know if still encountered. |
Description:
If you try and fail to configure Telegram access and just leave it there, nchat starts in loop trying to login again and again:
This will go on so long that machine either totally freezes or puts out OOM error and forekills nchat.
How to reproduce it:
Setup Telegram and fail, don't remove config of it
Environment:
Additional info
I did not test if failure in Whatsapp does same, nor did I test anything else, this just bugged me for half of year and I wish no one else should suffer from this.
The text was updated successfully, but these errors were encountered: