Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Kidhack
9 years agoHelpful | Level 5
In a "mdworker quit unexpectedly" loop after turning on Smart Sync
Ever since turning on Dropbox Smart Sync, Spotlight has been going nuts and using tons of CPU. The helper app "mdworker" is constantly crashing. Will report back after Dropbox finishes indexing all t...
- 8 years ago
Hi everyone,
I wanted to give you an update on the issue of mdworker crashing when reading a mismatch in the expected logical vs physical size of PDFs on Mac.
Firstly we've not forgotten about this, a lot of work has been going on in the background to resolve the issue. It has required extensive code re-writing. For those not familiar with the issue, users may see within the logs mdworker crashing. This crash is fairly silent, though will appear in logs. There's no risk to data, but for those who like to inspect clean logs this can cause a lot of noise and may be viewed as sub-optimal.
Based on the feedback raised by yourselves on this forum we've spent considerable time working toward a fix. We've changed the way we write Smart Sync placeholders (ie the files that look like files, but take up 0kb until recalled) for those on 10.13.5 and later. The new sparse format will not trigger an mdworker crash.
We've tested within the beta to validate the code and at this point have now rolled the fix / changed behavior out to 100%.
This is a forward fix, so from now on all and any placeholders created will not suffer this issue. For those who have the placeholders (the empty files with the grey cloud symbol on them) already on their machines there are a few options:
- Unlink and relink your Dropbox. Note: this will trigger a reindex of content that may take minutes to a few hours depending on your filecount.
- Remove the content, via Selective Sync, then return it. Similarly, but perhaps preferably, this will remove the placeholders then re-add them quickly and non-destructively.
There are a few other options, but those keen to avoid this error being highlighted in logs can take these steps.
Many thanks for your feedback on this issue here, it's driven a clear change in product. We pay close attention to the feedback surfaced via this channel so if you have other wishes please either add to existing threads, up-vote ideas, or create your own thread to spark discussion or development.
Vera77
8 years agoExplorer | Level 3
Ok, I see! I dont Think I have the
Knowledge to do that you did myself... This came up when updated the dropbox app. Hmm Maybe need to get some help.
Thanks!
Knowledge to do that you did myself... This came up when updated the dropbox app. Hmm Maybe need to get some help.
Thanks!
Walter
Dropbox Community Moderator
8 years agoHey there Vera77 - can you first try re-installing our software using our latest stable build of the desktop application as 53.4.66 just got out (yesterday) and let me know if you notice the same behavior?
Let me know how this goes please!
Thank you for sharing all the troubleshooting process you went through Kevin - I appreciate it. Just to see if this is somehow related, could you let me know if you stopped seeing this issue while on our latest build - currently 53.4.66 ?
Thank you both for your replies.
- Kevin H.228 years agoExplorer | Level 4
Walt -
I went through the reinstall steps early last week, so if it was just released yesterday - it was using an earlier version.
That old profile is long gone, so I don't have the means to restore it and find out if upgrading would resolve it as I cannot reproduce the defect any longer.
K
- Walter8 years ago
Dropbox Community Moderator
Thanks for the update Kevin H.22 - Happy you managed to resolve your concern in the end.
Feel free to reach back should you need anything else.
Take care!
- Vera778 years agoExplorer | Level 3Cross My fingers... Reinstalled the application. So far no crash...😊👍🏼
- Vera778 years agoExplorer | Level 3
Crashed again... mdworker...
- zoecml8 years agoNew member | Level 2Same here. I reinstalled the OS (High Sierra), but the error messages came back. So I uninstalled Dropbox --> No more crashes.
I then tried reinstalling Dropbox but the error messages are now back. - Kevin H.228 years agoExplorer | Level 4
What finally worked for me was a complete reinstall.
0. prep for reimage: move all 'data' files you care about into a dropbox folder (or other off-client storage)
0a: I didn't do this, but one might consider also making a backup to a cloud that can be restored as insurance.
0b: now might be the time to get that password manager you've been thinking about...
1. Boot mac into recovery mode CMD+R.
2. Run First-Aid on HD
3. Erase HD
4. Run First-Aid on HD (just for good measure)
5. Reinstall High Sierra
6. Create new profile (no restoring from backup or migrating or the issue will persist - at least it persisted for me)
7. Reconfigure your favorite changes to the OS preferences and settings
8. Download and Re-install desired applications
9. Set dropbox preferences / smartsync etc
K
- Fabio L.8 years agoExperienced | Level 12
Crash also on my side with latest High Sierra. Now I managed to solve the issue forcing Spotlight do not scan files within the "Dropbox" Folder. Once I let him scan, the system crashes with mdworker issues.
About Integrations
Find solutions to issues with third-party integrations from the Dropbox Community. Share advice and help members with their integration questions.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!