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

Excessive CPU usage while on Reply or Quote Tweet screens #22

Open
Aerospace35 opened this issue Nov 13, 2022 · 1 comment
Open

Excessive CPU usage while on Reply or Quote Tweet screens #22

Aerospace35 opened this issue Nov 13, 2022 · 1 comment

Comments

@Aerospace35
Copy link

It's me again! I Established an instance of this site and have made some improvements that I will upload to GitHub soon. One thing I couldn't solve was a sudden spike and sustained high levels of processor usage when clicking on the comment or entering the quote tweet views, from the home feed. This causes mobile browsers to kill the site, and severely stresses the speeds of the site on desktops and laptops. I think it has something to do with the CSS or rendering of the popup somehow, because as soon as I click off the tab, the usage drops. It is also possible it has something to do with the javascript, I am not sure. Regardless, I cut out a bunch of CSS code that didn't need to be there, and I got the usage down by 10%- but it still won't function properly on mobile browsers. I can confirm however, that invoking the reply and quote popups from the status page (after clicking on a tweet in the timeline) functions as expected. I tested this on a fresh instance, and same issues. Website crashed on iPhone 8 running Safari on iOS 16, as well as a Macbook Pro running Monterey, and was slow on my trusty Thinkpad T500 running Debian and Firefox.

Link to my site, which I discovered the problem on, and the fresh instance (respectively)
https://spitter.loophole.site
https://spitter.loophole.site/spitter-project-master

@Serifarat
Copy link

because you are trying to upload thousands of tweets at the same time 😂 of course it will crash.
for this you need to list tweets, you need to limit it by pagination or load.
It has nothing to do with css or js.

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

2 participants