You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Dropbox Issues with Mac OS Mojave
Users on Mac OS Mojave are experiencing an issue with Dropbox, their computers have become extremely slow. It works fine when Dropbox is not running. When Dropbox app is relaunched, it takes about 3...
THANK YOU, firstlooks!
Your instructions finally worked, whereas everything else had failed. More detailed instructions for deleting the hidden folder can be found here:
Under Mojave, dropbox renders my computer unusable after about 10 minutes. It looks like the problem is I/O requests—either too many of them building up or somehow each one of them taking too long, but if I leave dropbox on, my laptop becomes completely unusable. If I turn off Dropbox, the computer recovers quite quickly. I have a lot of files on Dropbox, and use selective sync to turn them off. I here's hoping somewhat at Dropbox is paying attention to this.
Seems that Dropbox and Mojave are not compatible. It was a very painful 2 days of wasted time realsing this to be the case! - And strange that this is not flagged by Dropbox or Apple with some kind of warning not to upgrade to Mojave.
Mojave+Dropbox=crippled computer :(
Well, this isn't great, but it makes my computer usable again...I pieced together a command line that lowers dropbox's disk and cpu priority to the lowest setting. I can now print again in Mojave and use things that rely on dropbox folders. Somehow the I/O is getting queued in such a way that there's a huge backlog and it causes memory and cpu resource crunch. This seems to fix it for now:
sudo pgrep "Dropbox" | while read line; do sudo renice 20 -p $line ; done
what it does is "renices" all the dropbox processes to the lowest priority. It seems like doing this, and then rebuilding my metadata database with a
sudo mdutil -i on /
has made the problem better. YMMV. You will have to run the first command with each reboot. Hopefully that helps someone?
-eric
Thanks, but that's too much for me. It's strange that they are not trying to solve this. I was hoping the recent Mojave update would fix this, but wasn't the case. Two such companies that big, you'd think they would have the capacity for solving such bugs.
