-
Notifications
You must be signed in to change notification settings - Fork 13
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
The extension slows down Threads considerably #31
Comments
You have absolutely nothing to apologize for. Your work is great, and I appreciate the effort you put in. Thank you for responding so promptly. I'd already disabled that option earlier today, and all is good. I'll wait for the next version. |
Yes, unfortunately, the add-on slows down my Firefox even when the toggle switch for Threads is turned off. Threads only works at normal speed when the add-on is completely disabled. Additionally, the add-on is currently resource-hungry and causes the entire system to lag (i7 CPU 10th Gen, 32 GB RAM, PCIe SSD). When the add-on is active, Firefox's RAM usage briefly spikes. At its peak, I saw 7 GB instead of just over 3 GB without the add-on and the use of Threads. It's such a shame because I love the add-on, especially for Instagram, but for now, I'll keep it disabled and only enable it when I want to download something. Hopefully, there's potential for further improvements. Thanks for the hard work and for providing the add-on! |
I'm no longer seeing the CPU rise with the extension. I re-enabled all permissions a few weeks ago, and it's been fine. |
Haven't had this problem on Windows - maybe it's a Linux thing? |
Browser(Chrome/Firefox): Firefox on Ubuntu Linux
Extension Version: 2.1.7
Reproduction of links: Any threaded post on Threads.net
For the past couple of weeks I've noticed that Threads is unbearably slow. When I open a post to see the subsequent posts they can take up to 20 seconds to load. I disabled all the extension on my system and started testing each one. This one turned out to be the culprit.
The text was updated successfully, but these errors were encountered: