-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
More than 50 % cpu load on macOS Catalina #17125
Comments
happens on telegram 3.1 on windows from the microsoft store after leaving the app open for a day or so |
Recently I noticed that my Telegram Desktop is slower than before too, causing noticeable CPU load (30% on my laptop). I'm not sure if it's related to this issue or #17091, or my own environment. I don't know which version it started from. I'm using Ubuntu 18.04 (default theme), the Telegram Desktop app was installed from the Snap Store and it gets upgraded automatically every time when a new version is released. Update (FWIW): |
Hey there! This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own. Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue. Thanks! |
still an issue |
Hey there! This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own. Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue. Thanks! |
still an issue |
@ask-compu The issue is about macOS Catalina, you write about Microsoft Store version. For me the Windows version doesn't consume too much CPU, 0% while idle. Can you give some details in your case? |
it seems somewhat random but it stops if i close and reopen the telegram window (not quitting, still running in the background), i always leave telegram's window open and idk what causes the issue |
Hey there! This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own. Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue. Thanks! |
this still happens sometimes, it's rare tho |
Same issue on Macos Ventura |
Hey there! This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own. Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue. Thanks! |
r the devs ignoring this? |
Well, I have no idea how to reproduce the bug. |
Same issue mac os 12.6.8 I think Telegram doesn't want to fix this issue cause this may be a big consumer CPU-GPU and maybe calculating something in clients' pcs. |
Same CPU loads here. On Fedora 39 & 40 and Gentoo + macOS 14.5 (23F79) Sonoma + Windows 11 @john-preston It doesnt matter If I now use the official Telegram Client for the PC (Yes, from the website or here, Github) or even a third party provider like 64Gram. This has to be a bigger issue since it affects all common systems: Also to be said, the iOS App has the same issue, but not always. Theres a bit less load when the App is running in the background, but still keeping the CPU hooked up. (Luckely, Desktop only) |
It might also to be said and maybe the reason for that...I have everywhere older CPU's for daily tasks in use. Intel: fifth and sixth Gen Intel i5 CPUs |
Same issue Mac OS 15.0 on M3, Telegram 5.5.5. |
Steps to reproduce
start telegram, leave it opened.
Expected behaviour
low cpu consuming
Actual behaviour
more then 50 % loading
Operating system
Mac OS Catalina 10.15.7
Version of Telegram Desktop
3.1.9
Installation source
Static binary from official website
Logs
No response
The text was updated successfully, but these errors were encountered: