Rpcsvchost mac os грузит процессор
Slowdown issues are a natural upshot of a Mac starting to age and lacking the resources to support increasingly resource-intensive applications. If the machine’s hardware is upgradeable, one decent workaround is to install more RAM and replace the standard “spinning” storage media with a faster SSD drive. But what if the performance of a brand-new or recently released MacBook, iMac, Mac Pro is running slower than usual? This condition requires some insight into the whys. Many users who run into such a situation and open the Activity Monitor to do some reconnaissance discover that a process named WindowServer is constantly using up most of the CPU resources. In many cases, this drag co-occurs with abnormally high memory consumption. This bug doesn’t appear to survive Mac reboots, but this measure has a short-time effect and the issue eventually re-emerges. It’s worth mentioning that the WindowServer related bug is often observed alongside unproportioned CPU consumption by the following processes: nsurlsessiond, mdnsresponder, mds_stores, hidd, trustd, photoanalysisd, gamecontrollerd and syslogd.
So, what is WindowServer on a Mac? And why does its CPU usage occasionally skyrocket? Let’s try to figure out. First things first, here is some wiki stuff on this matter: WindowServer is a collection of services tasked with window management. It is also defined as a compositing engine responsible for reflecting application behavior on the Mac’s screen. The core macOS process sits in between the programs you run and their graphical manifestation you see on the display. It is executed once you log in and stops running as soon as you log out. Whenever you’re using an app, surfing the web via your browser, seeing an ad online, or playing a game, WindowServer is the entity that enables you to view it all dynamically. Therefore, it is a hugely important and harmless system element. This doesn’t mean that it operates flawlessly at all times, though.
Special Offer
Malware causing WindowServer to use a lot of CPU may re-infect your Mac multiple times unless you delete all of its fragments, including hidden ones. Therefore, it is recommended to download Combo Cleaner and scan your system for these stubborn files. This way, you may reduce the cleanup time from hours to minutes. Download Now Learn how ComboCleaner works. If the utility spots malicious code, you will need to buy a license to get rid of it.
One of the widely reported scenarios where WindowServer consumes too much CPU and RAM is related to connecting an external monitor to a Mac machine. The adverse occurrence is more likely if it’s a 4K monitor. Also, a lot of users notice the bug after enabling a scaled resolution on a Retina display. Improper implementation of transparency effects can be another reason for the unwanted activity. This overlapping of factors suggests that the problem may kick in when the normal graphics rendering process becomes more complex due to a specific set-up and resolution tweaks. Some users have bumped into the quandary right after updating to macOS Catalina 10.15, the previous version of Apple’s operating system. An upgrade to macOS 11 Big Sur isn’t always smooth in this regard either. Ideally, a glitch like that shouldn’t be observed in either case, but it’s often there and it needs immediate fixing. The affected machine runs hot for a long time and works slower than it should. Sometimes the buggy activity leads to kernel panics, a condition where the Mac crashes and the user cannot get it back on track easily.
As mentioned above, the WindowServer high CPU usage predicament is often encountered as part of a more unnerving whole. If you head to the Utilities and launch the Activity Monitor, you may notice several more processes collectively consuming the greater part of the central processing unit’s resources. Here’s a brief description these entities that may turn into CPU hogs out of the blue:
- Nsurlsessiond. This is a process involved in syncing a Mac user’s images, contacts, and other data with the iCloud server.
- Mdnsresponder. This one is a zero-configuration networking service that allows Apple devices to spot each other on the same network and share content such as iTunes libraries. Mdnsresponder a constituent of the so-called Bonjour protocol.
- Mds_stores. It’s a component of the Spotlight search feature. One of its functions is to index files stored on the Mac.
- Hidd. The acronym stands for “human interface device daemon”. Its role is to interpret all the events associated with your mouse and keyboard usage.
- Trustd. This is a daemon that manages and verifies digital certificates to make sure the running processes are code-signed and can be trusted. It also checks if websites encrypt the connection and are safe to visit.
- Syslogd. Maintenance of system logs is what the syslogd process does. It performs, among other things, the compression of these logs to optimize their size and make sure they don’t take too much space on disk.
A whole separate facet of abnormal Mac CPU usage by WindowServer and the processes listed above is in the security area. These bugs may be the way some malware strains signal their presence on a Mac computer. Cybercriminals aren’t likely to engage in extensive testing of their harmful code, which could lead to malfunctions when a system is infiltrated behind the scenes. Adware apps that target web browsers are also known to waste a ton of CPU resources by overburdening legitimate macOS services. Therefore, if your computer’s processing power is being permanently exhausted by the processes described in this tutorial, checking it for malicious activity is just as important as finding and tackling regular system malfunctions.
Get rid of resource-intensive malware in web browser on Mac
To begin with, the web browser settings taken over by the virus exploiting WindowServer process should be restored to their default values. Although this will clear most of your customizations, web surfing history, and all temporary data stored by websites, the malicious interference should be terminated likewise. The overview of the steps for completing this procedure is as follows:
-
Remove malware in Safari
Open the browser and go to Safari menu. Select Preferences in the drop-down list
How do you delete Activity Monitor on Mac?
That’s a strange question, isn’t it? You can’t delete Activity Monitor on Mac. It’s hard-coded into the system and does a bunch of incredibly useful things. Believe it or not, though, some users put it that way while implying something like this: “How do you stop a process using Activity Monitor on Mac?” Let’s set the formulation quirk aside and move on to the answer.
To quit a process that’s causing issues, expand the “Go” menu in the Finder toolbar, select “Utilities”, and double-click the Activity Monitor icon. The app provides a breakdown of active processes by the following categories: CPU, Memory, Energy, Disk, and Network. Just click the appropriate tab in the upper part to enable the required view. Then, select the executable you want to terminate, click the button with the X symbol in it, and use the “Quit” or “Force Quit” option on the popup dialog to stop it from running.
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]
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.
Picho13
macrumors newbie
I have been dealing with a pretty nasty problem ever since I upgraded to High Sierra and it has to do with iconservicesagent and external hard drives that have files with custom icons.
It first happened when I plugged in an external hard drive after upgrading from Sierra to High Sierra. iconservicesagent basically went crazy and used an astonishing 32GB (yes, GB) of physical RAM on my computer, before running out and continuing to use the SSD space via swap memory to keep using RAM until it ran out of space on the SSD. I first though it was a problem with permissions, ACL's and such, so I tried repairing those, no dice.
Went and did a clean install of High Sierra and the exact same problem happened as soon as I plugged in the external hard drive.
I have custom icons for my files on that hard drive (by copying and pasting a photo to the icon on the "get info" panel) and that is what is driving the CPU and RAM usage thru the roof.
I have a maxed out late-2015 iMac 5K with a Core i7 6700K and 32GB of RAM and the whole thing comes down to a crawl when iconservicesagent goes berserk. Finder completely stops responding until I reset the computer or disconnect the external hard drive.
I tried formatting the drive to APFS and same thing happened. Only when I removed the custom icons from the files, did iconservicesagent not go crazy, but this is not an option for me and is a problem that wasn't present in Sierra.
I have also tried clearing caches, rebuilding databases, swapping hard drives and nothing fixes this problem.
Any ideas or someone with a similar problem?
Attachments
Fory360
macrumors newbie
Hi, I have the same problem and apple says to reinstall, I already did it 3 times and it still does not recognize the bug.
I have a htpc with 8tb of videos with their custom icons and for me it is a real annoyance since I can not open any file, iconservicesagent goes crazy and I can not do anything just disconnect the hard disks and only work with the disk of installation of high How do you remove custom icons? I can not even open the finder with the hard disks connected as it goes crazy the finder and it does not respond
PicnicTutorials
macrumors 6502a
I have been dealing with a pretty nasty problem ever since I upgraded to High Sierra and it has to do with iconservicesagent and external hard drives that have files with custom icons.
It first happened when I plugged in an external hard drive after upgrading from Sierra to High Sierra. iconservicesagent basically went crazy and used an astonishing 32GB (yes, GB) of physical RAM on my computer, before running out and continuing to use the SSD space via swap memory to keep using RAM until it ran out of space on the SSD. I first though it was a problem with permissions, ACL's and such, so I tried repairing those, no dice.
Went and did a clean install of High Sierra and the exact same problem happened as soon as I plugged in the external hard drive.
I have custom icons for my files on that hard drive (by copying and pasting a photo to the icon on the "get info" panel) and that is what is driving the CPU and RAM usage thru the roof.
I have a maxed out late-2015 iMac 5K with a Core i7 6700K and 32GB of RAM and the whole thing comes down to a crawl when iconservicesagent goes berserk. Finder completely stops responding until I reset the computer or disconnect the external hard drive.
I tried formatting the drive to APFS and same thing happened. Only when I removed the custom icons from the files, did iconservicesagent not go crazy, but this is not an option for me and is a problem that wasn't present in Sierra.
I have also tried clearing caches, rebuilding databases, swapping hard drives and nothing fixes this problem.
Any ideas or someone with a similar problem?
This affects me too. I can tell when I see my ram drop 1GB a second. Seems to need two things in tandom to turn iconservicesagent into a cpu/memory whore. Finder and navigating an external drive. Until apple gets off their butt you can use forklift (finder replacement). Seems to prevent the issue.
GuilleA
macrumors 6502
When you say custom icons, are you referring to when Finder displays covert art for a MP3/AAC file or a poster for a TV Show/Movie file? Or for files and folder you have set customs icons?
I have one of my Minis with High Sierra with an external USB hard drive in which I store my iTunes media library. I Have hundreds of m4v files with customized icons and I don't have this problem.
Fory360
macrumors newbie
When you say custom icons, are you referring to when Finder displays covert art for a MP3/AAC file or a poster for a TV Show/Movie file? Or for files and folder you have set customs icons?
I have one of my Minis with High Sierra with an external USB hard drive in which I store my iTunes media library. I Have hundreds of m4v files with customized icons and I don't have this problem.
Attachments
GuilleA
macrumors 6502
That's f**ked up. Are the images embedded in the files? Which software are you using for custom icons? I do all my m4v files with Subler, which add the posters and TV show art to the files.
Fory360
macrumors newbie
That's f**ked up. Are the images embedded in the files? Which software are you using for custom icons? I do all my m4v files with Subler, which add the posters and TV show art to the files.
GuilleA
macrumors 6502
Ok, have you tried embedding the art in the files and let Finder display it as an icon as I'm doing? Perhaps the issue lies in the amount of icons it needs to render. Do a test with folder and see if removing the icons doesn't fire up RAM usage, and then use something like Subler to embed the art into the files.
Fory360
macrumors newbie
I think it would not be a good option, keep in mind that the files I am referring to are MKV UHD between 30 GB and 60 GB and I do not want to change extension or recode the video, nor is it that I know very well how subler works.
J.Gallardo
macrumors 6502
I have been dealing with a pretty nasty problem ever since I upgraded to High Sierra and it has to do with iconservicesagent and external hard drives that have files with custom icons.
It first happened when I plugged in an external hard drive after upgrading from Sierra to High Sierra. iconservicesagent basically went crazy and used an astonishing 32GB (yes, GB) of physical RAM on my computer, before running out and continuing to use the SSD space via swap memory to keep using RAM until it ran out of space on the SSD. I first though it was a problem with permissions, ACL's and such, so I tried repairing those, no dice.
Went and did a clean install of High Sierra and the exact same problem happened as soon as I plugged in the external hard drive.
I have custom icons for my files on that hard drive (by copying and pasting a photo to the icon on the "get info" panel) and that is what is driving the CPU and RAM usage thru the roof.
I have a maxed out late-2015 iMac 5K with a Core i7 6700K and 32GB of RAM and the whole thing comes down to a crawl when iconservicesagent goes berserk. Finder completely stops responding until I reset the computer or disconnect the external hard drive.
I tried formatting the drive to APFS and same thing happened. Only when I removed the custom icons from the files, did iconservicesagent not go crazy, but this is not an option for me and is a problem that wasn't present in Sierra.
I have also tried clearing caches, rebuilding databases, swapping hard drives and nothing fixes this problem.
Any ideas or someone with a similar problem?
An idea:
Normal icons are low size files; but even with those files, system makes a lot of thing regarding them. (relative sizes & effects, animations. for example).
I think when you paste a big size image to make an icon in info window system doesn’t reduce its weight.
Perhaps you could get things to work better by reducing image mb size. I’m not near a mac now to confirm, but I believe you can do it in Preview, or “GraphicConverter”. Maybe you could batch-process all those images to a reasonable low weight (color bit depth, pixels). You can keep the video file intact, but try to make your icons something system is more used to manage.
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.
Helloha
macrumors member
OMG, why is the accountsd (mail) process using all CPU resources when there is no wifi connected? As soon as I enable wifi CPU usage drops to nothing.
This has been an issue for me for the past month or so (I think since updating to catalina) .
Am I the only one?
Thanks for any input!
K.
mdmitris
macrumors newbie
lpuerto
macrumors regular
I'm in the same boat as you… I guess that the only workaround is to close mail everytime you close the lid, because I caught my mac also woke up with the lid closed and with fans full speed because this issue.
lpuerto
macrumors regular
This is specially dangerous if you have power nap on and the connection drops after go to sleep —at it should even more in some cases like when you are doing tethering— you can wake up or come across a quite nosy and overheating mac. It juts happened to me tonight. Let's hope 10.15.2 fix this issue.
mdmitris
macrumors newbie
lpuerto
macrumors regular
Digging down a little bit more, the issue seems related to exchange account. At least in my case. That's probably why some people was also reporting it if they keep calendar open.
PS/ I can confirm that if you disable exchange account there is no issue. In other words perhaps apple is not the culprit.
mdmitris
macrumors newbie
The same here. If you disable exchange, everything works fine (POP3/IMAP). As a temporary measure, I had to switch from Exchange to IMAP to connect to the Office 365 tenant. Hopefully it will be fixed soon.
lpuerto
macrumors regular
I guess this is quite difficult to notice, because not everyone has a exchange account on mail —a lot of people is using outlook for work accounts— and we live in an hyperconnected world where usually there is internet everywhere. So, no network situation is quite rare. I was able to notice because I was in hospital with the computer and there I needed to use tethering for internet… so I had the issue when closing the lild with the computer connected to power and power nap fired up.
I really hope the issue is fixed on 10.15.2 and we can forget about this.
mdmitris
macrumors newbie
lpuerto
macrumors regular
Yep! It's true, it's still not fixed…
elnbrg
macrumors member
Sad but true. Moving to IMAP instead of Exchange. Very disappointed in Apple not fixing bugs that are critical for business. They add useless emojis and fix bugs in the News app - the app that is used by only a small percentage of users, but they don't care about mission-critical apps like Mail. I am starting to think that Thunderbird and Outlook for Mac will work better on my Mac than the stock Mail app.
lpuerto
macrumors regular
Sad but true. Moving to IMAP instead of Exchange. Very disappointed in Apple not fixing bugs that are critical for business. They add useless emojis and fix bugs in the News app - the app that is used by only a small percentage of users, but they don't care about mission-critical apps like Mail. I am starting to think that Thunderbird and Outlook for Mac will work better on my Mac than the stock Mail app.
The thing is, have you reported the bug? I've done now twice. I really think it's a pesky error, since most people is connected all the time to internet. Probably test at Apple are like that, they are connected to the internet all the time and they haven't noticed. It's not an excuse, since you have to test your system in&out and upside&down, but… probably is the reality.
myret
macrumors newbie
I simply stopped using mail app and went back to Spark app. I am happy no issues no extensive CPU usage and no fan noise. I think apple becomes worse and worse on Mac OS updates.
lpuerto
macrumors regular
Apple is become not as good as it was in customer support. Now there are more hollow and scripted answers that only make customer lose their time.
I understand that there could be bugs, it the nature of any system, but c'mon!
[automerge]1576083560[/automerge]
This is quite common behavior in customer support, you try to show the customer that the problem is in their side so you have to fix, instead of check right away if they can reproduce and acknowledge the problem.
lpuerto
macrumors regular
By the way, and for the sake of testing. I opened my account on safe more and also created a new user account and the results were exactly the same. When there was no connection, if mail is open and an exchange account enabled, accountsd goes berserk.
I did this because apple asked me to do that on a post in the official communities, and I told them that it was bollocks! Which it is… but just to be on the safe side, I just did it, and I got the same result (of course).
elnbrg
macrumors member
elnbrg
macrumors member
I think I found a fix to this problem.
Please follow these steps:
1. Make a backup of Apple Mail messages if you store anything locally (like storing something On My Mac, downloading via POP3 etc).
2. Go to System Preferences > Internet Accounts.
3. Delete all Exchange accounts.
4. Delete ~/Library/Mail and ~/Library/Containers/com.apple.mail folders (this will reset Apple Mail and its preferences).
5. Restart the Mac and uncheck "Reopen windows when logging back in" to make sure Apple Mail won't start after rebooting.
6. Go to Internet Accounts, click on +, select Exchange, enter your name and email address.
7. Click on Configure Manually and enter your password.
8. Uncheck everything (like Contacts, Notes, Calendar etc) and leave only Mail checked. You will be able to add it later (see below).
9. Start Apple Mail and go to Preferences > Accounts.
10. Select your Exchange account and click on Server Settings tab.
11. Uncheck "Automatically manage connection settings".
13. Close Preferences and restart Apple Mail.
14. If you need Contacts and Calendars, go to System Preferences > Internet Accounts, select your Exchange account and enable the services you need to sync.
Thats it. I was waiting for 2 days and it's been working fine so far, no CPU spikes when no connection, accountsd and Mail processes are quiet.
Let me know if it helps or if you have any other questions regarding this.
Замедление работы — следствие старения конкретного Mac-устройства и нехватки ресурсов для поддержания более ресурсоемких приложений. Это естественный процесс. Когда железо все еще можно прокачать, проблему можно решить посредством установки большего объема оперативной памяти (ОП) и замены штатного носителя данных с вращающимися элементами (HDD) на более быстрый SSD-накопитель. Но что, если производительность совершенно нового или недавно выпущенного MacBook, iMac, Mac Pro ниже чем обычно? Давайте разберемся, что к чему! Многие пользователи в подобной ситуации открывают Мониторинг Системы, чтобы изучить работу процессов на компьютере. Они обнаружат, что процесс с именем WindowServer на постоянной основе использует большую часть ресурсов ЦП. Во многих случаях, эта аномалия происходит одновременно с чрезвычайно высоким потреблением памяти. После перезагрузки Мак симптомы исчезают, но только на время, и проблема в конечном итоге возникает снова. Стоит отметить, что баг, вызываемый WindowServer, часто наблюдается на фоне непропорционального потребления ресурса ЦП следующими процессами: nsurlsessiond, mdnsresponder, mds_stores, hidd, trustd и syslogd.
Что представляет собой WindowServer в системе Mac? И почему загрузка ЦП временами так взлетает? Давайте попробуем разобраться. Перво-наперво, вот некоторые вики-материалы по этому вопросу: WindowServer — это набор служб, которые выполняют задачу управления окнами. Его также определяют как комплексный механизм, который выводит приложения на экран Mac. Коренной процесс macOS протекает между выполняемыми программами и их графическим отображением на экране. Он запускается при входе в систему и прекращается при выходе из нее. Работаете с программой? Просматривайте сайты в Интернете с помощью браузера? Увидели рекламу онлайн? Играете на компьютере? Именно WindowServer обеспечивает Вам динамический просмотр соответствующей информации. Следовательно, это чрезвычайно важный и по определению безвредный элемент системы. Это, впрочем, не означает, что он всегда работает безупречно.
Один из широко известных сценариев, при которых WindowServer потребляет слишком много ресурсов ЦП и оперативной памяти, связан с подключением внешнего монитора к компьютеру Mac. Такое неблагоприятное событие более вероятно, если это 4K монитор. Кроме того, многие пользователи отмечают появление данной проблемы после включения масштабированного разрешения на дисплее Retina. Неправильная реализация эффектов прозрачности может быть еще одной причиной нежелательной активности. Такое наслаивание факторов предполагает, что проблема может возникать тогда, когда обычный процесс визуализации графики усложняется из-за определенных настроек и регулировки разрешения. Некоторые пользователи сталкиваются с затруднениями непосредственно после обновления системы Apple до macOS Catalina 10.15 — текущей версии операционной системы. В идеале, подобный сбой не должен наблюдаться ни в одном из этих случаев, но на практике он часто возникает и требует немедленного исправления. В результате компьютер предельно загружен и работает медленнее, чем должен. Иногда этот баг вызывает kernel panics, состояние, при котором Mac выходит из строя, а отрегулировать его весьма непросто.
Опять же, беда не приходит одна. Истощение ресурса ЦП часто вызывает комплексная нагрузка, WindowServer создает только ее часть. Если перейти в меню Утилиты macOS и запустить Мониторинг Системы, можно заметить еще несколько процессов, коллективно потребляющих большую часть ресурсов центрального процессора. Вот краткое описание процессов Мак, которые имеют свойство внезапно превращаться в настоящих пожирателей ресурса ЦП:
- Nsurlsessiond. Процесс, связанный с синхронизацией изображений, контактов и прочих данных пользователя Mac с сервером iCloud.
- Mdnsresponder. Это сетевая служба с нулевой конфигурацией, которая позволяет устройствам Apple обнаруживать друг друга по одной сети и обмениваться контентом, к примеру библиотеками iTunes. Mdnsresponder является составной частью так называемого протокола Bonjour.
- Mds_stores. Это компонент средства поиска Spotlight. Одной из его функций является индексация файлов, хранящихся в Mac.
- Hidd. Аббревиатура означает «human interface device daemon» (демон интерфейса устройства пользователя). Его роль — интерпретировать все события, связанные с использованием мыши и клавиатуры.
- Trustd. Это демон, который управляет цифровыми сертификатами и проверяет их, чтобы убедиться, что текущие процессы подписаны кодом и им можно доверять. Он также проверяет, шифруют ли веб-сайты соединение и безопасны ли они для посещения.
- Syslogd. Функция процесса syslogd заключается в ведении системных журналов. Среди прочего, он выполняет сжатие этих журналов, чтобы оптимизировать их размер и убедиться, что они не занимают слишком много места на диске.
С кибер-безопасностью связан целый отдельный аспект аномальной загрузки ЦП в Mac сервисом WindowServer и процессами, перечисленными выше. Эти нарушения могут сигнализировать о присутствии определенных штаммов малвари на компьютере Mac. Маловероятно, что киберпреступники будут проводить всестороннее тестирование своего вредоносного кода, что может приводить к сбоям при закулисном проникновении в систему. Также известно, что рекламные приложения, нацеленные на веб-браузеры, тратят массу ресурсов ЦП, оказывая чрезмерную нагрузку на легитимные службы macOS. Поэтому, если рабочую мощность вашего компьютера постоянно истощают процессы, описанные в этом руководстве, проверка его на вредоносную активность так же важна, как обнаружение и устранение регулярных сбоев системы.
What is Kernel_task on a Mac?
Kernel_task is an important service that prevents a Mac’s CPU from overheating. It kicks in when the operating system identifies an abnormally high resource usage that causes a considerable increase of the central processing unit’s temperature. Under adverse circumstances like that, this maintenance instrument automatically takes on an active role in curbing CPU-intensive processes to reduce the heat. When viewed in the Activity Monitor app, this routine sometimes appears bizarre because the amount of CPU power used by Kernel_task may exceed 100%, which doesn’t make much sense.
Manual removal of viruses causing WindowServer high CPU usage problem
The steps listed below will walk you through the removal of this malicious application. Be sure to follow the instructions in the specified order.
-
Expand the Go menu in your Mac’s Finder bar and select Utilities as shown below.
As an illustration, here are several examples of LaunchAgents related to mainstream Mac infections: com.pcv.hlpramc.plist, com.updater.mcy.plist, com.avickUpd.plist, and com.msp.agent.plist. If you spot files that don’t belong on the list, go ahead and drag them to the Trash.
The system will display the list of items launched when the computer is starting up. Locate the potentially unwanted app there and click on the “-” (minus) button.
How do I make my Mac run smoother?
If the performance of your Mac has taken a nosedive, there’s a handful of techniques to speed it up. Identifying the main reason for a slowdown will provide actionable insights into what area of the system needs fine-tuning in the first place. For instance, if too many apps are launched at startup, you should audit the list and eliminate redundant items. If you are low on disk space, it’s time to clean some junk. Scenarios vary, but the following tips help address most system productivity issues:
- Go to System Preferences > Users & Groups and remove unnecessary Login Items.
- Pinpoint and terminate resource-heavy processes.
- Release disk space by deleting clutter such as application caches and logs.
- Uninstall apps you don’t use.
- Install the latest macOS update.
- Check your Mac for viruses and remove everything dodgy you detect.
- If you are using an HDD, replace it with a Solid State Drive (SSD).
- Install more RAM if your Mac supports hardware upgrades.
Удаление вручную вирусов, вызывающих проблемы с высокой загрузкой ЦП сервисом WindowServer
Изложенные ниже шаги позволят Вам удалить это зловредное приложение. Обязательно следуйте инструкциям в указанном порядке.
-
Разверните меню Переход на панели Finder Вашего Mac и выберите вкладку Утилиты, как показано ниже.
В качестве иллюстрации, вот несколько примеров из LaunchAgents, связанных с распространенными инфекциями Mac: com.pcv.hlpramc.plist, com.updater.mcy.plist, com.avickUpd.plist, и com.msp.agent.plist. Если обнаружите файлы, которые не принадлежат к списку, просто перетащите их в Корзину.
Система отобразит список процессов, которые запускаются при включении компьютера. Найдите там потенциально нежелательное приложение и нажмите кнопку «-» (минус).
Use automatic tool to fix the WindowServer Mac issue
The Mac maintenance and security app called Combo Cleaner is a one-stop tool to detect and remove WindowServer virus. This technique has substantial benefits over manual cleanup, because the utility gets hourly virus definition updates and can accurately spot even the newest Mac infections.
Furthermore, the automatic solution will find the core files of the malware deep down the system structure, which might otherwise be a challenge to locate. Here’s a walkthrough to sort out the WindowServer issue using Combo Cleaner:
-
. When done, double-click the combocleaner.dmg file and follow the prompts to install the tool onto your Mac.
By downloading any applications recommended on this website you agree to our Terms and Conditions and Privacy Policy. The free scanner checks whether your Mac is infected. To get rid of malware, you need to purchase the Premium version of Combo Cleaner.
How do I fix WindowServer high CPU and memory usage Mac?
It depends on the root cause of the problem. If it occurs when you connect an external monitor to your Mac, change the screen resolution, or play around with transparency effects, the good news is that you aren’t dealing with a virus. In this scenario, try restarting your computer and see how it goes. Be sure to apply the latest macOS update, too. If none of this helps, go to System Preferences, select “Accessibility”, click “Display” in the sidebar, and enable the “Reduce transparency” option.
If the CPU and RAM overconsumption is happening without any graphics-related catalysts (that is to say, you haven’t changed any visual settings or plugged in an extra monitor), then you’ll need to check your Mac for malware. The guide above will point you in the right direction.
How do I free up memory on my Mac?
First things first, don’t confuse memory (RAM) with disk space. The former stores short-term data your apps require to run seamlessly, and the latter is the total storage capacity of your hard disk (HDD or SSD). When memory usage reaches a critical threshold, your Mac will become sluggish or even completely unresponsive. When faced with this kind of a nuisance, try a few best-practice methods to reduce RAM consumption and give the system a productivity boost.
- Restart your Mac.
- Explore the Memory tab in the Activity Monitor and quit RAM-intensive processes.
- Eliminate Login Items that don’t have to be executed at startup.
- Close unused browser tabs.
- Make sure you’re running the latest version of macOS.
Используйте автоматический инструмент, чтобы устранить проблему WindowServer в системе Mac
Приложение для обслуживания и безопасности Mac-компьютеров под названием Combo Cleaner - это универсальное средство для обнаружения и удаления вируса WindowServer. Этот метод имеет существенные преимущества по сравнению с ручной очисткой, поскольку утилита ежечасно получает обновления вирусных баз и может точно определять даже самые новые инфекции Mac.
Кроме того, автоматическое решение найдет основные файлы вредоносного ПО в глубине структуры системы, что может оказаться довольно трудоёмким при ручном поиске. Вот пошаговое руководство для решения проблемы WindowServer с помощью Combo Cleaner:
-
. Когда сделаете это, сделайте двойной клик на файл combocleaner.dmg и следуйте инструкциям по установке программы на Ваш Mac.
Загружая любые приложения, рекомендованные на этом сайте, вы соглашаетесь с нашими Условиями and Политикой Конфиденциальности. Бесплатный сканер проверяет, заражен ли ваш Мак. Чтобы избавиться от вредоносных программ, вам необходимо приобрести Премиум-версию Combo Cleaner.
Избавитесь от ресурсоемкой вредоносной программы в веб-браузере на Mac
Для начала необходимо вернуть настройки веб-браузера, нарушенные вирусом, использующим процесс WindowServer, в состояние по умолчанию. Это удалит большинство пользовательских конфигураций, историю веб-поиска и все временные данные, которые хранятся на веб-сайтах, но зато прекратит вмешательство вируса в работу браузера. Ниже изложены шаги для выполнения этой процедуры:
-
Как сбросить настройки в Safari
Откройте браузер и перейдите в меню Safari. Выберите Настройки в выпадающем списке.
Why is WindowServer running on my Mac?
Despite a good deal of negative feedback from users, WindowServer is a legitimate macOS process that plays an important role in enabling proper manifestation of graphical elements on the display. It is geared toward dynamic reflection of app windows and the embedded visual objects so that the user experience is seamless. Ideally, when you notice it running on your Mac, that’s perfectly normal.
In some situations, though, WindowServer may get out of hand by gobbling up most of the processor and memory resources. This likelihood of this drag increases when a user connects an external display to their Mac, especially one that supports 4K resolution. The problem may also be security-flavored: crudely made malware, crypto miners, and adware often impersonate benign system services and are to blame for slowing down a system to a crawl.
Читайте также: