You're right, of course. I normally follow that advice but I ran out of patience this time.
I can certainly get behind that; there are times when I'm troubleshooting a problem when I reach a point I stop caring about the exact cause of the problem and just want it to go away.
If coureservicesd was crashing, it's probably dumping the caches that fixed the problem. Among other things, coreservicesd provides icons for folders and files and provides information about the relationships between files and applications, and it can hang or crash if some of the cached information in the Launch Services database gets mangled.
