Announcement: Upgrade to macOS Mojave

With features like Dark Mode, Stacks, and four new built-in apps, macOS Mojave helps you get more out of every click. 
Find out how to upgrade to macOS Mojave > https://support.apple.com/macos/mojave

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

Question:

Question: lsd daemon 117% CPU

When Mac connected to iPhone via USB tethering, `lsd` daemon consumes 117% CPU. There are no oddities in Console. Any thoughts (or, better, solutions)?

MacBook Pro, macOS High Sierra (10.13.4)

Posted on

Reply

Page content loaded

Apr 19, 2018 7:51 PM in response to m_emelchenkov In response to m_emelchenkov

lsd in OS X is the LaunchServiceDaemon. launchd is a launch daemon manager! It provides probably the same function as in iOS. According to Apple, it provides support for launching apps and matching document types to apps. As a result, the keys recognized by Launch Services allow you to specify the desired execution environment for your bundled code. You might try rebuilding its database:

Rebuild LaunchServices Database


Open the Terminal application in your Utilities folder. At the prompt paste in the following command in its entirety:


find /System/Library/Frameworks -type f -name "lsregister" -exec {} -kill -seed -r \;


Press RETURN. Wait for the Terminal prompt to return after which you can quit the Terminal.

Apr 19, 2018 7:51 PM

Reply Helpful

Apr 19, 2018 8:06 PM in response to m_emelchenkov In response to m_emelchenkov

Use Activity Monitor to Kill Runaway Processes


Use Activity Monitor on your Mac

Runaway applications can shorten battery runtime, affect performance, and increase heat and fan activity.


Kill the process using Activity Monitor. Then rebuild the database. Restart and see if the problem is fixed. Perhaps lsd is trying launch software you have that is causing the problem. If this doesn't help then navigate to the /Home/Library/ folder. Look for anything with "com.apple.LaunchServices." in the filename. Select them and CTRL- or RIGHT-click on the selection. Choose Move to Trash from the context menu but do not Empty the Trash. Reboot the computer and see if the problem is fixed. If it is then Empty the Trash. If not the open the Trash and put the two items back from where you deleted them.

Apr 19, 2018 8:06 PM

Reply Helpful

Apr 19, 2018 8:37 PM in response to Kappy In response to Kappy

"Perhaps" is not the right word for diagnosis. It's a Windows approach—try this, try that. In Mac you can always diagnose what's going on. If not, and if rebuilding DB does not helps, that means a bug in core. High Sierra is the most buggy system after Show Leopard. Probably, I need to file a bugreport. But Apple anyway does not fix these bugs, which I reports, they are confirmed and opened for months and years. So... God bless it will be fixed sometimes.

Apr 19, 2018 8:37 PM

Reply Helpful

Apr 20, 2018 3:03 AM in response to m_emelchenkov In response to m_emelchenkov

In case you don’t know—ASC is a user to user discussion community. Apple’s only occasional participation here is by employee moderators, labeled as such. Feedback links (page bottom) to Apple are here:

Contact - How to Contact Us - Apple


Kappy, who’s a fellow user not an Apple rep, is trying to help you sort your issue. He/she’s very knowledgeable.

Apr 20, 2018 3:03 AM

Reply Helpful
User profile for user: m_emelchenkov

Question: lsd daemon 117% CPU