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
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...
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.
We are running the latest version. I submitted a ticket via your web interface last night, but I didn't seem to get a email response with a ticket number, so I don't know what it is. Let me know if there is another way we can get in touch and go over this.
Dropbox got back to my ticket and just suggested turning of mdworker, acting like that isn't a crucial part of the OS that many apps including Outlook use for their own search purposes. Looks like we won't be getting any significant help on this issue if that's all they are suggesting...sigh.
I am runing v25.4.28. Turning off mdworker is not an option as i still want spotlight to index.
I have noticed by lookng at the error reports that mdworker tends to fail while indexing PDFs.
II have not submitted a ticket yet.
Ticket submitted - but no number yet.
Further information from error report.
import fstype:hfs fsflag:480D000 flags:45E diag:0 isXCode:0 uti:com.adobe.pdf plugin:/Library/Spotlight/PDF.mdimporter - find suspect file using: sudo mdutil -t 160449924 Application Specific Signatures: import uti:com.adobe.pdf plugin:/Library/Spotlight/PDF.mdimporter uuid:7D48EF77-69AB-47DB-BBD9-D907F89C3C17 61
The PDF.mdimporter is always the culprit.
Be nice if we could just switch that off until someone sorts this issue.Very similar to what I am seeing. Hoping Dropbox actually sheds some light on this instead of telling people to turn off mdworker, such a cop out if that's the company line.
