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

Firefox extension utilizes lot of CPU #1333

Open
wslyvh opened this issue Feb 5, 2024 · 3 comments
Open

Firefox extension utilizes lot of CPU #1333

wslyvh opened this issue Feb 5, 2024 · 3 comments

Comments

@wslyvh
Copy link

wslyvh commented Feb 5, 2024

Every time I open up or try to do any action using the browser extension my CPUs go crazy.
I can actually hear them spin up. % usage jumps to ~!5%. The extension itself becomes really slow.
When I initially open it, it's basically unusable, so I wait 2-3 seconds to "cool down" to around 7-8% CPU usage, before clicking or performing any next action.

I've had this issue since the launch of the extension (Oct '23) and disabled it immediately again after installing.
There's some DM history on twitter (@wslyvh).

I recently formatted and did a clean install of OS + Browser + extensions, so wanted to give it another try but still experiencing the same issues.

Laptop: System76 Lemur Pro (11th gen, i7, 40GB ram)
OS: Pop_OS 22.04
Firefox version: 122.0
Rainbow extension version: 1.3.62

Only 1 wallet address is added: wslyvh.eth

@gvastethecreator
Copy link

same problem here, just uninstalled

@DanielSinclair
Copy link
Contributor

Hi folks! We are investigating and investing in fixes for this issue. We introduced our first performance improvement last week specifically for Firefox users that was related to overuse of the network RPC by our NFTs feature. We have found that Firefox seems to suffer unique performance issues for the new Manifest v3 extension standard, and have pinpointed some of these instances to network activity where Firefox's main thread will bog down during a swarm of network requests. This also appears to impact some operating systems more than others, including Linux distros where Firefox itself seems to be under optimized. We will continue to optimize our network activity to mitigate this, and are seeking additional performance gains around the codebase.

If you find specific reproduction paths or scenarios that worsen performance, or have additional insights or optimization ideas, definitely let us know. We are actively working on this, and will keep this thread updated as we make progress.

@gvastethecreator
Copy link

Hi folks! We are investigating and investing in fixes for this issue. We introduced our first performance improvement last week specifically for Firefox users that was related to overuse of the network RPC by our NFTs feature. We have found that Firefox seems to suffer unique performance issues for the new Manifest v3 extension standard, and have pinpointed some of these instances to network activity where Firefox's main thread will bog down during a swarm of network requests. This also appears to impact some operating systems more than others, including Linux distros where Firefox itself seems to be under optimized. We will continue to optimize our network activity to mitigate this, and are seeking additional performance gains around the codebase.

If you find specific reproduction paths or scenarios that worsen performance, or have additional insights or optimization ideas, definitely let us know. We are actively working on this, and will keep this thread updated as we make progress.

mainly while trying to sign anything it occurs, tried with brand new installations and everything.

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

No branches or pull requests

3 participants