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.
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
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.
I got is solved by reindexing Spotlight.
And for stubburn files that would not Smart Sync, duplicate the file, delete the old one, rename the copy – works fine √
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:
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.
The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.Sound good? Let's get started.
For more info on available support options, see this article.
If you found the answer to your question, please 'like' the post to say thanks to the user!