Take Your Search Game to the Next Level with Dropbox Dash 🚀✨ Curious how it works? Ask us here!
Forum Discussion
Dropbox using 7 processes and 234 MB of memory
My question is similar to this one: https://www.dropboxforum.com/t5/Apps-and-Installations/Why-are-7-versions-of-Dropbox-exe-running-on-my-Windows-11/td-p/610743, but in that question, the largest amount of memory used by any Dropbox process is 4.1 MB, and the total is 9.4 MB.
On my system, the Dropbox processes are (at the moment) using over 260 MB of memory. That seems unreasonable to me. My entire Dropbox folder is 872 MB, so the process memory is 30% the size of my Dropbox folder.
I shut down Dropbox, and immediately after restarting, it was using 276 MB. Over the next 30 minutes, it first decreased to 260.6 MB, then increased to 261 MB, then 282 MB.
Here's a screen shot of Windows Task Manager showing the memory usage:
Dropbox processes using 282184 KB of memory
My Dropbox version is 173.4.6706.
Is it normal for Dropbox processes to be using a quarter of a gigabyte of memory?
8 Replies
Replies have been turned off for this discussion
- Megan
Dropbox Staff
Hey DouglasInNewark, let's jump right into this!
As a first step, did you notice when this behavior started happening? Have you tried any of the troubleshooting steps mentioned in the thread that you linked, such as restarting the device, and the app?
Let me know more!
I just noticed it the day I posted the message. I think I went into task manager to kill some process, and noticed seven Dropbox tasks, and all the memory they were using.
I rebooted Windows, and Dropbox immediately grabbed something over 220 MB. I just restarted Dropbox. One process immediately ran its memory usage up to 198 MB. The next two biggest were about 10 and 20 MB. By the time I finished typing those sentences, it was up to about 260 MB total. So restarting Windows and Dropbox made no difference.
- Megan
Hey DouglasInNewark, can you let me know more, in regards to the app's syncing status currently?
Is it up-to-date or is it maybe stuck syncing content?
