Skip to content
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

Very high CPU usage #25

Open
tulku opened this issue Jul 24, 2018 · 2 comments
Open

Very high CPU usage #25

tulku opened this issue Jul 24, 2018 · 2 comments

Comments

@tulku
Copy link

tulku commented Jul 24, 2018

Webogram tends to use too much CPU, particularly much more than the normal Telegram web client.

Some screenshots of webogram CPU usage using chrome's resource monitor:
screenshot from 2018-07-24 14-47-22
screenshot from 2018-07-24 14-46-50
screenshot from 2018-07-24 14-46-04

While using the oficial client, the CPU usage was minimal:
screenshot from 2018-07-24 14-45-31

@pisti2010
Copy link

I have experienced the same. Some things I have noticed:

  • It does not happen all the time, I cant tell if it is random or what causes it.
  • I have seen that doing a refresh usually lowers the cpu usage.
  • The cpu usage increases over time in a peak like manner. For example while I write this I am looking at my cpu usage of webogram, it goes between 25% and 5%, then suddenly one goes to 30%, then it changes from a range of 25%-5% to 30%-10%... Weird.
  • I have seen thousands of this error in my browser console:
    app.js:70183 Uncaught DOMException: Failed to execute 'setItem' on 'Storage': Setting the value of 'ngStorage-snapshotsByMessageId' exceeded the quota.
    at https://webogram.ekumenlabs.com/js/app.js:70183:84
    at Object.forEach (https://webogram.ekumenlabs.com/js/app.js:1936:20)
    at https://webogram.ekumenlabs.com/js/app.js:70182:37

@berithpy
Copy link

I have experienced the same, a temporal fix I've been using is clearing the site's data and it works great for a couple of days!

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

No branches or pull requests

3 participants