Suddenly the lion became crawling tonight and the mbp cpu fan was 'shouting', i struggled to open the activity monitor and found out that the distnoted process was taking all the cpu time.
After I killed the distnoted, the system calmed down and then the distnoed appeared again but it was then harmonic.
It has happened twicely.
What is the matter?
Thanks.
MacBook Pro, Mac OS X (10.7.2)
Sounds like a problem with the distnoted process.
I don't know how to avoid this, I had thought the macbook pro does not have a cpu fan before this.😁
I found recently, that Skype was using the Distnoted process, and that there must have been a leak since it started slowly eating up processor time until it was at 100% of all of my processors. Skype then crashed. The present version is 5.0.6.143. I tested it again after a restart and saw the same leak. Hope this helps, at least a little.
I just turned it off and after having had the fan on FULL for 3 hours it just calmed down in 3 minuts and the the battery life is now over 6 hours instead of less than 2 hours.
THANK YOU
Permanent solution:
sudo mv /usr/sbin/distnoted /usr/sbin/crap_distnoted
ps -ef | grep noted
sudo kill -9 <PID>
The more I dig into this, the less I like it:
DISTNOTED(8) BSD System Manager's Manual DISTNOTED(8)
NAME
distnoted -- distributed notification server
SYNOPSIS
distnoted
DESCRIPTION
distnoted provides distributed notification services.
There are no configuration options to distnoted. Users should not run distnoted manually.
Mac OS X July 1, 2005 Mac OS X
What kind of crap manual page is this???
WHAT IS IT DOING, WHY and WHEN??
Second thoughts.. DON'T this appears to be a part of the kernel messaging system.. disabling it will lock you system and prevent it from booting cleanly, or at all !!!!
I have the exact same symptoms. Removed all apps from startup. Completing basic tasks in Apple applications and Shoah, distnoted running at 300% CPU, what on earth!?
Before I go into detail is this just effecting the two of us?
Matt
Much appreciated ds store, I was hoping someone had this specific issues rather than running through every diagnostic available. I appreciate the general guidance though and will retained have a look, although the first 4 have been completed already to no effect
Hi Matt.
All I did was go to the plantronics website and updated my software for the headset I use.
It was really simple and the problem has been gone for months.
This is a error with plantronics and Skype. This is why the possessor use all the power and the fan runs all the time.
Let me know if it works for you.
Ah thanks Kaffka,
Skype has gone and I have no headset at all so that's odd and surely can't be the case. What a puzzling problem, which is killing my CPU and battery, let alone my wooden laptop stand!
I am having a similar issue with my imac, can anyone help me ?
24-inch, Early 2008
Processor 3.06 GHz Intel Core 2 Duo
Memory 4 GB 800 MHz DDR2 SDRAM
I can not add anymore physical ram
Graphics NVIDIA GeForce 8800 GS 512 MB
Software OS X 10.8.3 (12D78)
7/18/13 11:20:20.926 AM com.apple.SecurityServer[15]: Session 100005 created
7/18/13 11:22:27.000 AM kernel[0]: Sandbox: sandboxd(371) deny mach-lookup com.apple.coresymbolicationd
7/18/13 11:22:36.025 AM sandboxd[371]: ([351]) QuickLookSatelli(351) deny file-read-data /Users/samurai/Music/iTunes 2012-02-16/iTunes Library.itl
7/18/13 11:22:36.072 AM sandboxd[371]: ([351]) QuickLookSatelli(351) deny file-read-data /Users/samurai/Music/iTunes 2012-02-16/iTunes Library.itl
7/18/13 11:22:36.127 AM sandboxd[371]: ([351]) QuickLookSatelli(351) deny file-read-data /Users/samurai/Music/iTunes 2012-02-16/iTunes Library.itl
7/18/13 11:22:36.151 AM sandboxd[371]: ([351]) QuickLookSatelli(351) deny file-read-data /Users/samurai/Music/iTunes 2012-02-16/iTunes Library.itl
7/18/13 11:22:36.192 AM sandboxd[371]: ([351]) QuickLookSatelli(351) deny file-read-data /Users/samurai/Music/iTunes 2012-02-16/iTunes Library.itl
7/18/13 11:22:36.204 AM sandboxd[371]: ([351]) QuickLookSatelli(351) deny file-read-data /Users/samurai/Music/iTunes 2012-02-16/iTunes Library.itl
7/18/13 11:22:36.240 AM sandboxd[371]: ([351]) QuickLookSatelli(351) deny file-read-data /Users/samurai/Music/iTunes 2012-02-16/iTunes Library.itl
7/18/13 11:23:34.645 AM Locum[413]: Connection with distnoted server was invalidated
7/18/13 11:23:39.000 AM kernel[0]: Sandbox: sandboxd(414) deny mach-lookup com.apple.coresymbolicationd
7/18/13 11:23:43.590 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:23:44.217 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:23:55.241 AM Locum[422]: Connection with distnoted server was invalidated
7/18/13 11:23:56.037 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:23:56.664 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:24:08.130 AM Locum[424]: Connection with distnoted server was invalidated
7/18/13 11:24:11.514 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:24:12.141 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:25:02.781 AM Locum[432]: Connection with distnoted server was invalidated
7/18/13 11:25:19.364 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:25:19.992 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:25:46.156 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:25:46.784 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:25:58.414 AM Locum[438]: Connection with distnoted server was invalidated
7/18/13 11:26:00.446 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:26:01.073 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:26:13.714 AM Locum[439]: Connection with distnoted server was invalidated
7/18/13 11:26:15.598 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:26:16.225 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:26:31.755 AM Locum[440]: Connection with distnoted server was invalidated
7/18/13 11:26:35.714 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:26:36.342 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:26:52.902 AM Locum[444]: Connection with distnoted server was invalidated
7/18/13 11:26:53.765 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:26:54.393 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:36:12.147 AM Locum[484]: Connection with distnoted server was invalidated
7/18/13 11:36:20.364 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:36:20.998 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:36:48.000 AM kernel[0]: considerRebuildOfPrelinkedKernel prebuild rebuild has expired
7/18/13 11:37:32.644 AM Locum[496]: Connection with distnoted server was invalidated
7/18/13 11:37:33.689 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:37:34.316 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:37:47.417 AM Locum[499]: Connection with distnoted server was invalidated
7/18/13 11:37:48.252 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:37:48.900 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:38:09.407 AM Locum[500]: Connection with distnoted server was invalidated
7/18/13 11:38:18.093 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:38:18.720 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:38:34.224 AM Locum[504]: Connection with distnoted server was invalidated
7/18/13 11:38:34.602 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:38:35.245 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:39:47.010 AM Locum[511]: Connection with distnoted server was invalidated
7/18/13 11:39:49.225 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:39:49.852 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:40:13.217 AM Locum[514]: Connection with distnoted server was invalidated
7/18/13 11:40:15.230 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:40:15.858 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:41:21.435 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:41:22.062 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:41:35.793 AM Locum[525]: Connection with distnoted server was invalidated
7/18/13 11:41:38.719 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:41:39.348 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:41:55.316 AM Locum[528]: Connection with distnoted server was invalidated
7/18/13 11:41:57.099 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:41:57.723 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:42:39.015 AM Locum[529]: Connection with distnoted server was invalidated
7/18/13 11:42:45.024 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:42:45.651 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:43:55.489 AM Locum[536]: Connection with distnoted server was invalidated
7/18/13 11:44:07.482 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:44:08.108 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:44:58.404 AM Locum[544]: Connection with distnoted server was invalidated
7/18/13 11:45:09.779 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:45:10.406 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:45:25.735 AM Locum[547]: Connection with distnoted server was invalidated
7/18/13 11:45:34.407 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:45:35.005 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:46:02.003 AM Locum[551]: Connection with distnoted server was invalidated
7/18/13 11:46:13.137 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:46:13.765 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:46:39.674 AM Locum[552]: Connection with distnoted server was invalidated
7/18/13 11:46:47.277 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:46:47.904 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:47:28.203 AM Locum[555]: Connection with distnoted server was invalidated
7/18/13 11:47:31.456 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:47:32.082 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:48:12.000 AM Locum[561]: Connection with distnoted server was invalidated
7/18/13 11:48:17.935 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:48:18.562 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:49:42.246 AM Locum[571]: Connection with distnoted server was invalidated
7/18/13 11:49:52.014 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:49:52.641 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:50:27.816 AM Locum[575]: Connection with distnoted server was invalidated
7/18/13 11:50:31.078 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:50:31.705 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:50:49.150 AM Locum[578]: Connection with distnoted server was invalidated
7/18/13 11:51:20.280 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:51:20.908 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:51:35.473 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:51:36.102 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:51:55.214 AM Locum[585]: Connection with distnoted server was invalidated
7/18/13 11:51:55.871 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:51:56.498 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:52:25.496 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:52:26.123 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
7/18/13 11:52:40.220 AM Locum[590]: Connection with distnoted server was invalidated
7/18/13 11:52:43.704 AM coreaudiod[169]: Disabled automatic stack shots because audio IO is active
7/18/13 11:52:44.331 AM coreaudiod[169]: Enabled automatic stack shots because audio IO is inactive
Hi there,
I’m having this problem too. I just systematically went through all the apps I had open, closing them one at a time while watching the distnoted process for changes. My experience: Upon closing GNU Emacs distnoted stopped using my CPU up. I was then able to reopen emacs without distnoted using up lots of CPU again but I’m willing to bet after using it for a while it will start to cause a problem again.
Could it be that some apps can create infinite loops of kernel messages between processes or something similar?
I can confirm that GNU Emacs also seems to be related to high distnoted resource usage. Upon killing emacs, with xcode, chrome, itunes, etc. still open, distnoted usage went down from 100% cpu and 5.5 GB of ram to essentially 0 cpu and ~150mb of ram.
My 2009 Mac Pro computer started to bog down about a month or two ago. It finally reached the point where it was unusable (even the browser was freezing up for long periods of time). So I took the plunge and just reinstalled my Mac Pro from the original Snow Leopard DVD, then did all the upgrades to Mavericks. Even after that... it was still impossibly slow. So I started to google it, and got here. I have a process called distnoted that us using up as much CPU as it can, usually 90%. And I just finished a clean reinstall! How can a clean Mac Pro have such a problem?
Due to the fact that I just did a fresh reinstall of the OS, it's either a problem with the OS or a problem with my hardware. A few years ago I added three more hard drives to the one that came with this computer. Maybe I have to remove them to see if they are the problem. Or maybe some other piece of hardware is causing this, like the video card. But I haven't made any hardware changes in several years. The only hardware change was adding three more hard drives.
When I first bought this Pro in 2009 I did have a somewhat similar problem, the machine wouldn't boot. The authorized repair depot said my hard drive was causing the problem, so they replaced it under warranty. Maybe one or more of my hard drives is doing something nasty again.
The distnoted process took all the cpu time, the system kept crawling until i killed the distnoted process.
