Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: mattwallace
mattwallace Author
User level: Level 1
0 points

Coreduetd continuously crashing; stops spotlight from working

I have a brand new 12" Macbook. It is using a time machine restore from a retina MBP that was on 10.9 when the backup was made.


The symptom that made me notice this was that spotlight crashes - when hitting cmd+space, as soon as I unfocus from spotlight (whether by hitting enter or escape or clicking a result), it crashes. The actual search and display works fine, only when it is closing does it crash out. This causes it to lock up and freeze on the screen for 10+ seconds until OSX decides it is really dead and culls it. The part of spotlight still on the screen gives a beachball.


Activity log shows:


8/11/15 6:05:53.030 PM Spotlight[34535]: Hang timer fired; exiting

8/11/15 6:05:55.522 PM Spotlight[48607]: applications query - started

8/11/15 6:05:55.789 PM Spotlight[48607]: applications query - finished in 0.27 seconds



I've seen other issues on the forums where this is occurring and the fix is usually to remove /var/db/CoreDuet/* and reboot. I've done that. Yet it does appear that coreduetd is nevertheless the problem because mine is continuously crashing:

Aug 11 18:10:15 dynamo com.apple.xpc.launchd[1] (com.apple.coreduetd[48664]): Service exited due to signal: Abort trap: 6

Aug 11 18:10:15 dynamo com.apple.xpc.launchd[1] (com.apple.coreduetd): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

Aug 11 18:10:24 dynamo.local coreduetd[48665]: -[__NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x137

Aug 11 18:10:24 dynamo.local coreduetd[48665]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x137'

*** First throw call stack:

(

0 CoreFoundation 0x00007fff8d62903c __exceptionPreprocess + 172

1 libobjc.A.dylib 0x00007fff93a6a76e objc_exception_throw + 43

2 CoreFoundation 0x00007fff8d62c0ad -[NSObject(NSObject) doesNotRecognizeSelector:] + 205

3 CoreFoundation 0x00007fff8d571e24 ___forwarding___ + 1028

4 CoreFoundation 0x00007fff8d571998 _CF_forwarding_prep_0 + 120

5 coreduetd 0x000000010184a14b coreduetd + 41291

6 coreduetd 0x000000010184d36a coreduetd + 54122

7 coreduetd 0x00000001018734fe coreduetd + 210174

8 coreduetd 0x0000000101863d72 coreduetd + 146802

9 libdyld.dylib 0x00007fff93e9a5c9 start + 1

)

Aug 11 18:10:25 dynamo com.apple.xpc.launchd[1] (com.apple.coreduetd[48665]): Service exited due to signal: Abort trap: 6

Aug 11 18:10:25 dynamo com.apple.xpc.launchd[1] (com.apple.coreduetd): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.



etc. Happens continuously. I've been googling for doesNotRecognizeSelector errors crashing coreduetd, and I've seen a lot of that issue but only 1-2 reports of that with coreduetd, and all of those were fixed by removing /var/db/CoreDuet/*


Does anyone have some insight?

Posted on Aug 11, 2015 5:12 PM

Reply
8 replies
User profile for user: mattwallace
mattwallace Author
User level: Level 1
0 points

Aug 11, 2015 9:47 PM in response to Linc Davis

No change.


Aug 11 22:42:03 dynamo.local WindowServer[172]: disable_update_timeout: UI updates were forcibly disabled by application "Spotlight" for over 1.00 seconds. Server has re-enabled them.

Aug 11 22:42:03 dynamo.local spindump[486]: Got xpc error message in libspindump client connection: Connection invalid

Aug 11 22:42:05 dynamo.local coreduetd[488]: -[__NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x137

Aug 11 22:42:05 dynamo.local coreduetd[488]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x137'

*** First throw call stack:

(

0 CoreFoundation 0x00007fff83bdd03c __exceptionPreprocess + 172

1 libobjc.A.dylib 0x00007fff8a01e76e objc_exception_throw + 43

2 CoreFoundation 0x00007fff83be00ad -[NSObject(NSObject) doesNotRecognizeSelector:] + 205

3 CoreFoundation 0x00007fff83b25e24 ___forwarding___ + 1028

4 CoreFoundation 0x00007fff83b25998 _CF_forwarding_prep_0 + 120

5 coreduetd 0x000000010024114b coreduetd + 41291

6 coreduetd 0x000000010024436a coreduetd + 54122

7 coreduetd 0x000000010026a4fe coreduetd + 210174

8 coreduetd 0x000000010025ad72 coreduetd + 146802

9 libdyld.dylib 0x00007fff8a44e5c9 start + 1

)

Aug 11 22:42:05 dynamo com.apple.xpc.launchd[1] (com.apple.ReportCrash.Root[489]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash.DirectoryService

Aug 11 22:42:06 dynamo com.apple.xpc.launchd[1] (com.apple.coreduetd[488]): Service exited due to signal: Abort trap: 6

Aug 11 22:42:06 dynamo com.apple.xpc.launchd[1] (com.apple.coreduetd): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

Aug 11 22:42:15 dynamo.local coreduetd[490]: -[__NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x137

Aug 11 22:42:15 dynamo.local coreduetd[490]: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x137'

*** First throw call stack:

(

0 CoreFoundation 0x00007fff83bdd03c __exceptionPreprocess + 172

1 libobjc.A.dylib 0x00007fff8a01e76e objc_exception_throw + 43

2 CoreFoundation 0x00007fff83be00ad -[NSObject(NSObject) doesNotRecognizeSelector:] + 205

3 CoreFoundation 0x00007fff83b25e24 ___forwarding___ + 1028

4 CoreFoundation 0x00007fff83b25998 _CF_forwarding_prep_0 + 120

5 coreduetd 0x0000000105b1614b coreduetd + 41291

6 coreduetd 0x0000000105b1936a coreduetd + 54122

7 coreduetd 0x0000000105b3f4fe coreduetd + 210174

8 coreduetd 0x0000000105b2fd72 coreduetd + 146802

9 libdyld.dylib 0x00007fff8a44e5c9 start + 1

)

Aug 11 22:42:17 dynamo.local WindowServer[172]: disable_update_likely_unbalanced: UI updates still disabled by application "Spotlight" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

Aug 11 22:42:17 dynamo com.apple.xpc.launchd[1] (com.apple.coreduetd[490]): Service exited due to signal: Abort trap: 6

Aug 11 22:42:17 dynamo com.apple.xpc.launchd[1] (com.apple.coreduetd): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

Aug 11 22:42:26 dynamo.local coreduetd[493]: -[__NSCFNumber isEqualToString:]: unrecognized selector sent to instance 0x137


Time machine backup on a Synology dj410j. I started using this Mac in ~2007 and have been rolling it forward since, though, so I think this is its 4th instance. The last migration (from a 17" MBP to the first of the Retina MBPs) worked great and was off the Synology also and produced no issues. This macbook was fresh from the box and I picked the time machine backup from the normal new-mac menu, and it saw the backup on the wifi immediately with no issues and appeared to restore with no problems, and I haven't seen any other issues other than Spotlight crashing.


Also, you're awesome, thanks for all your posts in here. (Saw all your replies when looking for answers to this.)

Reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Aug 11, 2015 10:27 PM in response to mattwallace

Please read this whole message before doing anything.

This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.

Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem?

After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Aug 14, 2015 9:42 AM in response to mattwallace

If you don't already have a current backup, back up all data, then reinstall the OS.* You don't need to erase the startup volume, and you won't need the backup unless something goes wrong. If the system was upgraded from an older version of OS X, you may need the Apple ID and password you used.

There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it. The same goes for Xcode. All other data will be preserved.

*The linked support article refers to OS X 10.10 ("Yosemite"), but the procedure is the same for OS X 10.7 ("Lion") and later.

Reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Aug 19, 2015 12:12 PM in response to mattwallace

The warranty entitles you to complimentary phone support for the first 90 days of ownership.

If you bought the product in the U.S. directly from Apple (not from a reseller), you have 14 days from the date of delivery in which to exchange or return it for a refund. In other countries, the return policy may be different. If you bought from a reseller, its return policy applies.

Reply
User profile for user: mattwallace
mattwallace Author
User level: Level 1
0 points

Aug 25, 2015 8:08 AM in response to Linc Davis

So, I have AppleCare. Phone support basically suggested a fresh install without time machine restores; and said they'd replace the hardware if it continued to fail (which, of course, it won't, because coreduetd getting an unrecognized selector isn't a hardware problem), or suggested manually moving my applications. Of course, moving apps isn't the big deal - I want all my keychain entries, app prefs, and the rest of the universe of thing that comes with a 9-year-running time machine.


So it was:

launchctl unload /System/Library/CoreDaemons/com.apple.coreduetd.osx.plist

mv /System/Library/CoreDaemons/com.apple.coreduetd.osx.plist ~matt/tmp


for me. With coreduetd off, the crashing of spotlight stopped, and I guess I just won't be able to try using handoff until I'm willing to invest a lot of time manually migrating loads and loads of stuff. I might try a genius bar appointment if I had any confidence they could escalate to an actual engineer with a debugger, but I don't.


Appreciate the efforts, Linc.

Reply

Coreduetd continuously crashing; stops spotlight from working

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up