Both processes constantly uses 50-60% cpu on background and its making my Macbook very slow. How can I fix it?
MacOS Tahoe 26.1 Macbook Air M1 Dropbox App 238.3.5842
Hey @igoroliveiragg - thanks for bringing this to our attention.
Can you please quit the Dropbox desktop app and relaunch and/or reboot your computer as well and let me know if this persists?
If it does, you can try installing the latest, stable version of the Dropbox desktop app as you're now running a beta version.
Just make sure to toggle off the 'early releases' from your account's settings first.
Let us know of any updates!
Did all that, both processes (GPU and Renderer) still has high CPU usage, from the moment you start the app.
Same for me on an iMac 2020. I keep reading that it was sorted in the latest version but no luck for me. Had no problems on the previous OS but Tahoe is constantly using both GPU and CPU which is making everything very slow. The shell menu in Finder is also very slow to include the dropbox options. I'm assuming that is a connected issue.
Sorry to hear the issue persists, @igoroliveiragg.
Can you send me a screenshot of your current Dropbox app version, so that I can check this further?
Hey @Fugue! So, from what I understand this started happening right after upgrading to the latest macOS, correct?
Can you also clarify the Dropbox app version that you’re using?
Other than that, I’d like you to go through this Help Center article, if you haven’t already, and let me know if anything that’s mentioned there could also apply in your case.
Yes, it was the moment I upgraded the OS. GPU and CPU usage was fine before. Again, the dropbox shell menu wasn't the quickest to appear when DB was uploading/downloading but was definitely quicker before.
I'm on 237.4.5655
237.4.5655
I see, thanks for confirming @Fugue! I’ve gone ahead and logged a support ticket in our system for you.
Please check your email address’s inbox, when possible, and reply back to it; we’ll take it from there.
Thanks for that, @igoroliveiragg! I’ve also opened a separate ticket for you.
Please reply to it, when you see it, and we’ll look into this internally.
