Deleted mac os грузит процессор
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
the bug
macrumors regular
On my mid 2010 Mac Mini running 10.9.5 I noticed that every time I cold boot it the process "rpcsvchost" is using 99% of the CPU in activity monitor.
Most times rebooting takes care of it, until it sits powered off overnight, then on the first boot up it is back to eating 99% again.
I have reset SMC and PRAM, turned off all unnecessary items but it still continues.
I've searched online and found a few others that have had the same problem, but haven't found any answers.
Any advice would be appreciated, since I think my next step may be re-loading Mavericks.
Thanks in advance for any help.
the bug
macrumors regular
Wow, almost 100 views and nobody else has seen this.
Here's a little more info :
I reinstalled Mavericks last night and it seemed better after a couple of reboots, then today rpcsvchost was back up to using 99%.
It's running as root, so I don't think it's a startup item from any particular account.
Only a couple of entries in the console about it, I will post those and a spindump log below.
Very strange that it is only after it has been sitting off for a while.
9/25/14 6:31:25.000 PM kernel[0]: process rpcsvchost[89] thread 692 caught burning CPU! It used more than 50% CPU (Actual recent usage: 62%) over 180 seconds. thread lifetime cpu usage 90.015346 seconds, (71.342635 user, 18.672711 system) ledger info: balance: 90007778831 credit: 90007778831 debit: 0 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 143033006696
9/25/14 6:31:28.915 PM spindump[290]: Saved cpu_resource.spin report for rpcsvchost version . (. ) to /Library/Logs/DiagnosticReports/rpcsvchost_2014-09-25-183128_UpstairsMini.cpu_resource.spin
Command: rpcsvchost
Path: /usr/libexec/rpcsvchost
Version: . (. )
Parent: launchd [1]
PID: 89
Event: cpu usage (microstackshots only)
Thread: 0x2b4 (62% cpu over 146 seconds)
Duration: 146.00s
Steps: 98
Hardware model: Macmini4,1
Active cpus: 2
Fan speed: 1800 rpm
Powerstats for: rpcsvchost [89] thread 0x2b4
Start time: 2014-09-25 18:29:54 -0400
End time: 2014-09-25 18:31:25 -0400
Parent: launchd
Microstackshots: 76 samples (77%)
Primary state: 59 samples Non-Frontmost App, Non-Background Priority, User mode
User Activity: 0 samples Idle, 76 samples Active
Power Source: 0 samples on Battery, 76 samples on AC
76 thread_start + 13 (libsystem_pthread.dylib) [0x7fff90865fc9]
76 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff9086172a]
76 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff90861899]
76 proxy_start + 57 (DCERPC) [0x10782baa1]
67 timer_loop + 239 (DCERPC) [0x10785b439]
65 dcethread_cond_timedwait_throw + 11 (DCERPC) [0x10782d4f7]
31 dcethread_cond_timedwait + 111 (DCERPC) [0x10782d496]
28 __gettimeofday + 10 (libsystem_kernel.dylib) [0x7fff852e11cb]
17
2 _pthread_cond_wait + 142 (libsystem_pthread.dylib) [0x7fff908639f2]
1 _pthread_testcancel + 56 (libsystem_pthread.dylib) [0x7fff90862929]
1 DYLD-STUB$$OSSpinLockLock + 6 (libsystem_pthread.dylib) [0x7fff9086610a]
1 _pthread_cond_wait + 154 (libsystem_pthread.dylib) [0x7fff908639fe]
15 dcethread_cond_timedwait + 85 (DCERPC) [0x10782d47c]
6 dcethread__begin_block + 149 (DCERPC) [0x10782d073]
5 dcethread__unlock + 32 (DCERPC) [0x10782cbfe]
5 pthread_mutex_unlock + 60 (libsystem_pthread.dylib) [0x7fff908648f3]
2 OSAtomicCompareAndSwapLong$VARIANT$mp + 8 (libsystem_platform.dylib) [0x7fff8b640bd4]
2 __mtx_droplock + 590 (libsystem_pthread.dylib) [0x7fff9086450c]
1 __mtx_droplock + 615 (libsystem_pthread.dylib) [0x7fff90864525]
1 dcethread__debug_set_callback + 20 (DCERPC) [0x10782c0b5]
5 dcethread__begin_block + 141 (DCERPC) [0x10782d06b]
1 _pthread_cond_signal + 144 (libsystem_pthread.dylib) [0x7fff9086374a]
1 OSAtomicCompareAndSwapLong$VARIANT$mp + 8 (libsystem_platform.dylib) [0x7fff8b640bd4]
1 _pthread_cond_signal + 39 (libsystem_pthread.dylib) [0x7fff908636e1]
1 _pthread_cond_check_init + 6 (libsystem_pthread.dylib) [0x7fff90863ce9]
1 _pthread_cond_signal + 52 (libsystem_pthread.dylib) [0x7fff908636ee]
1 _pthread_cond_signal + 227 (libsystem_pthread.dylib) [0x7fff9086379d]
4 dcethread__begin_block + 38 (DCERPC) [0x10782d004]
3 dcethread__lock + 18 (DCERPC) [0x10782cb05]
1 _pthread_mutex_lock + 565 (libsystem_pthread.dylib) [0x7fff9086483a]
1 pthread_mutex_unlock + 223 (libsystem_pthread.dylib) [0x7fff90864996]
1 OSAtomicCompareAndSwapLong$VARIANT$mp + 8 (libsystem_platform.dylib) [0x7fff8b640bd4]
1 dcethread__lock + 89 (DCERPC) [0x10782cb4c]
13 dcethread_cond_timedwait + 144 (DCERPC) [0x10782d4b7]
6 dcethread__end_block + 28 (DCERPC) [0x10782d12c]
4 dcethread__lock + 18 (DCERPC) [0x10782cb05]
2 OSAtomicCompareAndSwapLong$VARIANT$mp + 8 (libsystem_platform.dylib) [0x7fff8b640bd4]
1 _pthread_mutex_lock + 229 (libsystem_pthread.dylib) [0x7fff908646ea]
1 _pthread_mutex_lock + 51 (libsystem_pthread.dylib) [0x7fff90864638]
1 pthread_threadid_np + 30 (libsystem_pthread.dylib) [0x7fff90861b43]
1 dcethread__lock + 53 (DCERPC) [0x10782cb28]
1 dcethread__lock + 65 (DCERPC) [0x10782cb34]
1 dcethread__sanity + 112 (DCERPC) [0x10782cd25]
4 dcethread__end_block + 96 (DCERPC) [0x10782d170]
3 dcethread__unlock + 32 (DCERPC) [0x10782cbfe]
1 pthread_mutex_unlock + 217 (libsystem_pthread.dylib) [0x7fff90864990]
1 pthread_mutex_unlock + 75 (libsystem_pthread.dylib) [0x7fff90864902]
1 pthread_mutex_unlock + 60 (libsystem_pthread.dylib) [0x7fff908648f3]
1 OSAtomicCompareAndSwapLong$VARIANT$mp + 8 (libsystem_platform.dylib) [0x7fff8b640bd4]
1 dcethread__unlock + 15 (DCERPC) [0x10782cbed]
1 dcethread__sanity + 101 (DCERPC) [0x10782cd1a]
2 dcethread__end_block + 88 (DCERPC) [0x10782d168]
2 OSAtomicCompareAndSwapLong$VARIANT$mp + 8 (libsystem_platform.dylib) [0x7fff8b640bd4]
1 dcethread__init_self + 75 (DCERPC) [0x10782caf3]
3 dcethread_cond_timedwait + 59 (DCERPC) [0x10782d462]
2 dcethread__self + 25 (DCERPC) [0x10782ca64]
1 pthread_once + 87 (libsystem_pthread.dylib) [0x7fff90862893]
1 dcethread__self + 37 (DCERPC) [0x10782ca70]
2 dcethread__new + 145 (DCERPC) [0x10782ca4b]
1 dcethread_cond_timedwait + 114 (DCERPC) [0x10782d499]
1 dcethread_cond_timedwait_throw + 37 (DCERPC) [0x10782d511]
1 mach_thread_self + 5 (libsystem_kernel.dylib) [0x7fff852de15f]
5 timer_loop + 73 (DCERPC) [0x10785b393]
5 rpc__clock_update + 33 (DCERPC) [0x10785a6df]
4 . [0]
3 __commpage_gettimeofday + 41 (libsystem_kernel.dylib) [0x7fff852ddbd9]
2 mach_absolute_time + 26 (libsystem_kernel.dylib) [0x7fff852dcca6]
1 mach_absolute_time + 28 (libsystem_kernel.dylib) [0x7fff852dcca8]
1 __commpage_gettimeofday + 83 (libsystem_kernel.dylib) [0x7fff852ddc03]
1 gettimeofday + 6 (libsystem_c.dylib) [0x7fff851051a9]
2 timer_loop + 78 (DCERPC) [0x10785b398]
2 rpc__timer_callout + 228 (DCERPC) [0x10785b87f]
2 timer_loop + 246 (DCERPC) [0x10785b440]
- Напоминаем, что эта проблема была исправлена в бета-версии 10.12.1 (16B2338c). deleted по-прежнему появляется время от времени, но он больше не потребляет столько, сколько ядро (с 25% до примерно 0,4% для меня).
- Ответ Оливера Мака самый лучший. Не пропустите!
Я пришел сюда из-за проблемы с моим MacBook Pro (2018 15 дюймов), работающим на macOS Catalina 10.15.7.
Фактически, deleted процесс отображался в моем списке процессов и потреблял около 50% ЦП - более или менее. Следуя некоторым подсказкам, которые я находил здесь и там (деинсталляция iStats, сброс SMC и т. Д.), Я понял, что этот процесс продолжался, пока мой Об этом Mac окно был открыт. В deleted процесс исчезает вскоре после закрытия Об этом Mac окно.
- Хорошая точка зрения. Я бы добавил, что этот процесс должен выполняться и займет время, когда вы попросите систему измерить объем хранилища и сколько места можно сэкономить, удалив локальные кэшированные копии облачных файлов или просто удалив большие файлы. Закройте окно, если вы не хотите, чтобы это измерение производилось сейчас.
- 6 Ух ты! Я могу подтвердить, что это правда. У меня есть deleted процесс запущен и потребляет процессор, несмотря на многочисленные попытки его убить. Я натолкнулся на этот ответ и, к своему удивлению, действительно Об этом Mac окно открыто все время. Я рад, что продолжал прокручивать. Примите мою благодарность!
- 1 Да, это было проблемой и для меня. Спасибо!
- 1 То же самое с «Дисковой утилитой», пока вы не закроете, выполняется процесс «удалено».
- Вау, это абсурдная ошибка. Я слышу «причину», которую дает bmike, но было бы плохим оправданием, если бы Apple попыталась ее использовать. Он постоянно забивает систему, даже если информация даже не видна, потому что она находится на скрытой вкладке. То же самое и с "Системной информацией"!
Для меня эта проблема была вызвана проблемами с меню iStat в macOS Sierra 10.12.0. Кажется, есть ошибка, которая вызывает проблемы с удаленным процессом. Как только я удалил iStat Menus, проблема исчезла.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
randolorian
macrumors 6502
Anyone seeing lots of Console and CPU activity from the "deleted" process? I've had the GM running for about 12 hours and this process just never seems to rest.
UPDATE: Turns out this was a caused by iStat Menus. Updating to build 687 seemed to resolve it.
simonmet
Cancelled
My uptime is 1.75 hours and deleted has 0.27 CPU time (which unit?). You?
Not doing much here.
Edit: Unit is "core minutes". Therefore it's effectively 4 seconds of 100% CPU usage on my system in 1.75 hours. I'm not sure how hyper threading counts however.
sddawson
macrumors member
Anyone seeing lots of Console and CPU activity from the "deleted" process? I've had the GM running for about 12 hours and this process just never seems to rest.
I tried Sierra beta for a short while on a 12" Macbook. Deleted used a lot more cpu time than on El Capitan. From memory, it hovered around 4-5% all the time, whereas on El Capitan it barely ever uses any. I'd be hesitant to upgrade if this issue still exists, and since you're on GM it sounds like it does. I need all the battery life I can get!
sddawson
macrumors member
Sierra final definitely still has this problem. Constant "deleted" process messages in the log, and CPU that is usually around 2-3%. Some sample messages:
default 22:11:31.180908 +1000 deleted : Successful Request
default 22:11:31.181030 +1000 deleted Connection to was invalidated.
default 22:11:31.181052 +1000 deleted tearing down extension request for pid 5275
default 22:11:31.181124 +1000 deleted Connection to was invalidated.
default 22:11:31.181279 +1000 deleted took 0.078833 seconds, returned:
default 22:11:31.181479 +1000 deleted updateInfo:
default 22:11:31.181607 +1000 deleted ENTRY, operation: CACHE_DELETE_PURGEABLE_OPERATION, serviceID: info:
default 22:11:31.181820 +1000 deleted updating cache for service: , volume: , amounts:
default 22:11:31.181923 +1000 deleted updating service info amount: 117834861, serviceID: , volume: , urgency: 3 pushed: FALSE
default 22:11:31.182008 +1000 deleted sendNotification: FALSE
default 22:11:31.183050 +1000 deleted PurgeableSpace result:
default 22:11:31.183312 +1000 deleted re-started persitence timer
default 22:11:31.183687 +1000 deleted SYNC purgeable op results:
That "tearing down extension request for pid" happens over and over for the processes MailCacheDelete, iTunesCacheExtension, iBooksCacheDelete and CacheDeletExtension. Cant be helping battery life!
EDIT: I set up a new userid. All the above processes appear soon after login, but disappear soon after, and deleted is under control. On my own username, those processes stay forever and deleted is out of control. Now just have to figure out why!
sddawson
macrumors member
On a fresh Sierra install, the processes MailCacheDelete, iTunesCacheExtension, iBooksCacheDelete and CacheDeleteExtension pop up at weird times. For instance, if you start Textedit they will start and run for a short time before disappearing (best way to see this is to have Activity Monitor running in its CPU tab and have "cache" in the search box). Also, if you start Preview and go to File, Open they appear the same way. Other apps they might appear when you start a save dialog. I have no idea what the processes do, and they even appear when you haven't logged into iCloud yet. However, they never hang around for long. In the Console log, you will see things like:
com.apple.appkit.xpc.openAndSavePanelService got a connection for: com.apple.cache_delete
Finder got a connection for: com.apple.cache_delete
Then a whole slew of messages start from the "deleted" process. But, as I said, the processes quit fairly quickly and no harm done. But, on my main machine with Sierra, the processes run non-stop and cause the CPU utilisation in the deleted process. So I started the process of finding out what was causing it. Well, turns out it's iStat Menus, if you have the Disks option checked. With it ticked, you get:
iStat Menus Status got a connection for: com.apple.cache_delete
Over and over, every 3 seconds. You have to untick and reboot to stop it. I'm going to contact the author and will post back.
bernie-uk
macrumors newbie
I had the same problem, which rendered the syslog and console useless, since they were filling up with 500 messages a second.
Launchd starts the agent com.apple.cache_delete which runs the process /System/Library/PrivateFrameworks/CacheDelete.framework/deleted. There are several cache extension that talk to deleted over XPC.
I created a new user as you mentioned above, and that does not have the problem.
I noticed there are some cache_delete setting files are in ~/Library/Caches/com.apple.cache_delete/
A solution that seems to work fine is move (or deleted) the ~/Library/Caches/ directory for the problem user.
I logged out of the problem account into another temp user, and with Terminal
$ sudo bash
$ cd /Users//Library
$ mv Caches Caches-tmp
Logged back in to original account and no more excessive logging.
Hope that helps.
sddawson
macrumors member
What happens once you've rebooted? Can you see all those cache processes I mentioned running (in CPU tab of Activity Monitor with "cache" as a search term)? On the new user, do you see the processes running every time you start Textedit, but then quit after maybe 30 seconds? Are you running iStat Menus?
So many questions!
But wait, there's more! Do you know what the deal is with Console under Sierra? You can't see any messages earlier than when you start looking at the log, and the contents of the log are completely different to previous OS versions. This is when clicking the name of your Mac in the left column. And boy is it verbose! Never seems to settle at all.
bernie-uk
macrumors newbie
Yes I do have iStat Menus which is running fine.
There is ionodecache and TMCacheDelete which are owned by root and use no CPU.
AssetCacheLocatorService is always there for my user, with zero CPU
There is a deleted for each user logged in, which always present at zero CPU.
As you observed, if I launch TextEdit (from either account) the follow processes are launched for BOTH logged in users for a few seconds, then disappear
CacheDeleteExtension
IDECacheDeleteAppExtension
iBooksCacheDelete
iTunesCacheExtension
MailCacheDelete
I tried other stock Apple apps to see if they did the same, but nothing launched. After playing around I think it is any app that supports iCloud Documents is causes a quick cache clear on launch (eg Automator). Non-iCloud apps don't do this.
The cache directory should just contains temporary app data (generally created by URL access using NSURLSession or NSURLConnection) which can be thrown away. The apps will recreate the folders when they are launched again.
Must agree, with each release of OS X, syslog just seems to be getting more verbose with all the background cloud processes and sandbox checks. The new console app is also using up more CPU and sometime hangs. Still getting use to it, but did find the old console more responsive and easier to use.
The whole logging system has been redesigned by Apple to better cater for the more segmented multi-process approach to apps. Since there are a lot more helper processes that apps spawn, and inter-process communication with XPC, it is harder to debug, so Apple introduced a concept of activities (new icon on the toolbar), which allows you to see a more complete message trail generated between the app and helpers.
Anyone knows what the 'deleted' process does and why it sometimes creates high CPU loads? Sometimes runs at 15 to 35%. But yesterday it even made the fan spin ridiculously high, due to +90% CPU usage for a long period.
I killed the process. But it came up again. I've rebooted, but it keeps coming up and keeps having that high CPU usage.
For those of you who are just reading this now, I fixed this issue (at least temorarily, hope it holds) by deleting everything in ~/Library/Caches
Just got this issue, and found your post. It's the new Apple Core Cache Delete Pro Framework. Looks like fresh bugs for 10.15.5. Looking at the spin dump, it seems to have one infinite loop where it's trying to rebase some data. Seems to start after I open the mail app, and it freezes and will crash the mail app.
I'm thinking this "Delete Helper" is deleting all the forgotten-or-chose-not-to-encrypt emails that Mail has been passing around in clear view for lord knows how long.
I'd just let it run for a while, and if the computer melts down, IDK, get a new gig or something. I used to stay a year behind on their updates. get the new stuff once it's patched.
Thanks! It must have been something to do with Mail indeed, because I do remember seeing something like this.
But it stopped showing up in Activity Monitor. Don't know what happened, or what hasn't been changed.
Maybe like you say , Mail is done deleting all those e-mails.
I just started having this problem. Never seen this before. Machine crashed, and when it came back up, deleted was sitting at about 25% CPU and won't go away, and other services are not coming up. New (~2months) 13" MacBook pro, running 10.15.6. Network won't come up.
EDIT/FOLLOW UP: Still not sure what caused the persistent deleted process, but the over-arching issue I was having after the crash seemed to be related to the (auto-launching) VPN being in some sort of inconsistent state at startup that was preventing the network from fully coming online.
Thanks! Found that one too. I don't have iStats, nor a console running full with deleted messages.
I "only" have since a few days suddenly the 'deleted' process running on high CPU usage. And when I kill it, it comes back again.
Seeing the same thing. 'deleted' is regularly around 10% CPU, eating my battery. 10.15.5, and not that much installed yet.
did anyone find a solution for this?
I had the same issue and looked through a lot of sites to find the answer, most sites recommend to replace the current admin profile with a new one. After looking through the 'Users & Groups', I found that there were a couple of Login Items that were no longer accessible due to them being deleted. After taking the apps off the login Items list, I saw the 'deleted' process was no longer on the of the activity monitor.
I am not sure if this was just a stroke of luck but I hope this helps😀
I just solved this problem by turning off the icloud drive, before that I also could not understand why the battery was melting before our eyes
I just solved this problem by turning off the icloud drive, before that I also could not understand why the battery was melting before our eyes
Still happening for me and I don't use iCloud. Any other ideas?
Just upgraded to 10.15.6 and this process is killing my performance and battery. Has switching to a new admin account been confirmed as a fix? One thread said it happened on a brand new device.
I wiped my drive and did a fresh install of 10.15.6 and am having horrible performance problems involving both this process and the diskarbitrationd. I am suspecting this may have to do with the shadow volume (" - Data" suffix) for the boot volume.
Some characteristics of my installation: I do not use iCloud, I have a third-party 2TB SSD, I'm on an older machine (late 2013 MacBook Pro), I have only one login item (Google Backup and Sync). I'm running Time Machine. Most of my software is pretty vanilla stuff. I don't don't run any developer tools aside from MySQL which is shut down 99% of the time. I see u/cotapaxi64 has also recently reported an issue. I would be interested in hearing more about your configs, third-party software you run, etc.
Hi, the activity monitor shows a process name "deleted" that is always running and uses a lot of o CPU (between 30 to 50%!). After I force to stop, it run automatically again, and again.
What is this process about?
MacBook Air 11", macOS 10.15
Posted on May 18, 2020 10:45 AM
Hi guys I have the same issue. For my 12 y/o daughter I purchased a brand new MB Air 2020 w/ the i5 upgrade (50 bucks). Unboxed it yesterday:
- created admin account for myself
- updated from 10.15.3 to 10.15.4 (took 45 mins to download and then almost an hour just to deploy update)
- created standard user account for my kid
- configured her account preferences
- installed no extra software
- Did not logout from my admin account
- gave it to her this morning at 9 am to use for school work,
- battery at 70%
- she used safari (google classroom) and watched a 5 min video and played some music, all using native apps
- within a couple of minutes (so she told me 45 mins later) the fans started to blow.
- 10 am: battery at 10%
- When I arrived at the machine the fans were Blowing max speed and continued to blow despite almost idle usage
- AM showed a process called “deleted” consuming around 30-60% CPU
- All she had active was one Safari Tab and music.
- cores 1-3-5-7 (In AM) were showing high Continuous loads:
- core 1: 90%
- cores 3 and 5: 50-60%
- core 7: 30%
- After 15 mins suddenly the fans Slowly went down, after half a minute they were silent.
@ TheLittles: my admin account was still running so I could be experiencing your scenario. Strange though: this is a brand new machine without legacy account debris.
- called apple support. They advised me to shut down and reset SMC. So I did.
- logged back on to my kids account only.
- started activity monitor, Safari, photos. After 3 hours of use: still no issues.
Could this be because of the admin user issue you mentioned?
Posted on May 20, 2020 5:01 AM
Helpful answers
Hi John, thanks a bunch for your clarification. Can you think of any circumstance how our 3 hour old MacBook Air 2020 (see my issue description above) could have got stuck in this deleted loop, which caused the fans to blow at top speed continuously and drained the battery from 70% down to 10% in just 45 minutes?
May 21, 2020 10:46 AM
There’s more to the conversation
Loading page content
Page content loaded
mirogarcia Said:
"'DELETED' PROCESS IN CATALINA Hi, the activity monitor shows a process name 'deleted' that is always running and uses a lot of o CPU (between 30 to 50%!). After I force to stop, it run automatically again, and again. What is this process about?"
Create a New Administrator User:
Its probably a stuck cache running in the current Administrator. So, create a New Administrator User, then delete this one from within it..
Are you logged in as an Administrator? Create a new Administrator user, and see if this still occurs while you are logged into a different Administrator user. If not, then it is something configured in your current user. So, from there move all of your files over to the new Administrator. Then, delete the current user you are having issue with. Just use this new Administrator account from here on out. You should be set from there.
Читайте также: