"du process" pops up and occupy 100% CPU

I didn't solve the issue. I've got a macbook pro 2010, partitioned with bootcamp and with os 10.6.8. "Du process" appears and disappears, and when pops up occupy 100% CPU. This process isn't present in my other macbooks with the same os. Is it possibile and useful (to get 100% cpu availability) to cancel it? How?
Thank you in advance for your help!

Safari third party plug-ins and extensions can increase CPU usage.
From the Safari menu bar click Safari > Preferences then select the Extensions tab. Turn that OFF, quit and relaunch Safari to test.
If that helped, turn one extension on then quit and relaunch Safari to test until you find the incompatible extension then click uninstall.
If it's not an extensions issue, try troubleshooting third party plug-ins.
Back to Safari > Preferences. This time select the Security tab. Deselect: Allow plug-ins. Quit and relaunch Safari to test.
If that made a difference, instructions for troubleshooting plugins here.

Similar Messages

Oracle occupy 100% CPU

Hi,
While running program from JDBC, Oracle process occupy 100% CPU. We have oracle 11gR2.we have 14GB RAM.Memory target is set to 4GB.can you please guide me how to troubleshoot.

user12116651 wrote:
While running program from JDBC, Oracle process occupy 100% CPU. We have oracle 11gR2.we have 14GB RAM.Memory target is set to 4GB.can you please guide me how to troubleshoot.Identify the physical o/s process consuming CPU via a command like top.
If this is an Oracle process, identify the session and process in the Oracle instance using the v$process and v$session views - the former contains the o/s process id and the latter is joined to get the Oracle session id and basic session details.
Next use the v$sess* views to analyse the wait states, events and statistics of that session. You can also determine the current SQL cursor being executed and use DBMS_XPLAN.display_cursor() to get its execution plan.
Details on the virtual performance v$ views are in the Oracle® Database Reference guide.

Firefox 3.6.12 is running extremely slow and taking 100% CPU on my mac.

Just updated Firefox to 3.6.12 and it's taking over 100% CPU on one of my processors and is running EXTREMELY slow, too slow to use.

Firefox used to be the doggs bollocks now its just a dog.
Back to internet exploder fro me im afraid.I cant keep waiting twenty seconds for everything its like being back in 1993.

CS6 and AME 100% CPU utilisation

So this is an odd question to ask maybe as we often asked for max CPU utilisation when encoding in the past to get stuff done quicker.
But - this is entirely new behaviour for me at least. I have a 6 core i7 X980 with HT and 24GB ram. In the past, I could queue up several sequences and let them encode to H.264 in the background while i carry on editing. Worked fine with no problems.
I recently upgraded my GPU to a 4GB GTX680 from a 1.2GB GTX570. There have also been 2 updates to PPro as well since I noticed this behaviour.
So the issue is that when encoding, all 12 threads are at 100% CPU utilisation and my mouse control suffers terribly - very very slow mouse as obviously there's not enough CPU resources to drive the pointer properly. This never happened in the past as CPU utilisation was never maxed out like this.
Anyone seen anything similar?
Thanks,
Paul.

Hi Darren,
I've not benchmarked the two cards in Premiere - I've not noticed any difference in real world use. Reading a few comparison reviews out there kind of said the same thing too (although gaming based reviews). The reason I went for the 680 was the availability of a 4GB VRAM model which was really important for me in After Effects using complex 3D models in the Video Copilot plugin, Element 3D.
So it was worth it for the memory but maybe not just for Premiere. I don't tend to do a load of video layers at once, the most is maybe a couple of layers PIP on virtual studio type projects but then most of them end up in AE really as its just hugely more flexible and fun to work with

"IMAQ Stop" takes 10sec to execute and consumes 100% CPU

Hi, I'm calling IMAQ Stop to end an acquisition but it consumes 100% of my processor and takes 10sec to complete (all the while consuming 100% CPU). In our application we start and stop the camera regularly and this is exactly when the user wants the program to be interactive so this 10sec delay is a big irritation to them.
My setup is - Dalsa Piranha line scan camera, RT 9 running on a desktop PC (it is compatible according to the test), PCI-1429 cameralink card.
Any help or comments welcome.
Thanks.
Solved!
Go to Solution.

Ah I have managed to solve this one, but first here are the answers to your questions:
Using Stop and then Close or just Close makes no difference. The Stop was taking so long that I simply used a probe before and after it on the error cluster and with 2009's probe timestamp function I could easily see how long it took. For more detailed timing analysis I use the us timer available with RT.
In any case, the way I solved the problem was by making sure that I stop the acquisition BEFORE the line clock to the camera is stopped. So IMAQ Stop probably waits for the end of the current frame before it returns - and if the line clock stops halfway through a frame (as was the case), a 10 sec timeout probably causes Stop to return eventually.
The line clock is being driven by a DAQ card (via RTSI) and I simply closed the session to that counter AFTER calling IMAQ Stop. The DAQ interface is not shown in the example above as it is coded in a different vi.
Thanks for all the help.

T41---process rundll32.exe occupied 100% cpu usage and caused slow performance.

hi i have a big problem whit the performance of my laptop. I bought a extra 4gb ram for the second slot that not exist; and still continuos getting my cpu usage at 100% whit 2 programs running like office and google crhome.
i have this specf of my latop:
- procesor: amd c-60 apu whit radeon hd graphics 1,00 ghz
- ram: 4gz
system type: 64-bit OS
winows 7 ultimate
please tell me if i have to install another OS, made changes in my configuration or just buy another laptop.
tks

Rundll32.exe Using High CPU on Windows 8.1
I use a Lenovo T440s laptop for my service calls and when I need to do work remotely. My laptop runs Windows 8.1 Professional. I love this laptop and it has proved to be tough as well as extremely fast. I noticed a couple weeks ago that my battery was going dead after about an hour of usage. I also noticed that my cooling fan in the laptop was running louder than normal. I decided to open Task Manger on my laptop to see what the issue was. I soon noticed that a process called rundll32.exe was using around 25 percent of my CPU. I killed the process and everything returned to normal.
A few days later, my battery was going dead very rapidly. My cooling fan was on almost constantly and was blowing warm air. I opened Task Manger and sure enough, rundll32.exe was using 25% of my CPU again. I killed the process and everything was fine. It wasn’t long and my laptop was doing the exact same thing as I described before. I decided it was time to get to the bottom of this issue. Here is how I troubleshot what program was using the rundll32.exe and in the process was killing my battery.
Step One: I downloaded Process Explorer. This is an excellent tool. It is similar to Task Manager but goes into way more depth on the processes and dlls that are running. I extracted the download and then ran Process Explorer as an administrator.
Step Two: One of the first things I noticed was rundll32.exe was using 23 percent of my CPU again.
I right-clicked on the rundll32.exe process and selected properties. I clicked on the Image tab and at once saw the culprit. A utility to monitor and gauge my battery usage, called PwrMgrBkGndMonitor, was draining my battery instead of saving it.
Step Three: After a little digging around in my installed programs I located a program called Lenovo Settings Dependency Package. PwrMgrBkGndMonitor was installed in the Lenovo Settings Dependency Package.
I didn’t use this program and decided I didn’t need it. I uninstalled the program and restarted my laptop. I haven’t had a problem with the rundll32.exe using up my CPU since I uninstalled Lenovo Settings Dependency Package.
If you are experiencing the same symptoms has stated above and you are running a Lenovo laptop with Windows 8.1, this may be your issue. However, before you uninstall the program I would recommend using Process Explorer. Process Explorer will help you determine the exact program that is giving you issues before blindly uninstalling and killing services. I hope my troubleshooting steps can help you find program is making rundll32.exe use high CPU usage. Let me know in the comments if this helped you!
Source: techspeeder.com

Opening VI and consuming 100% CPU power

I am trying to debug my VI. The first few times the VI ran well but suddenly the VI hang up. I have no choice but to end the LabView process using the Task Manager. When I try to restart this VI again, it fails to open and the Task Manager indicates that the LabView program is now consuming 100% of the CPU time but still fail to open this VI. Looks like it is entering into an infinite loop. I cannot fix anything for I cannot go into my VI to change anything. LabView just consumes all the CPU power and do nothing. What went wrong?
Regards,
Larry

Okay. That is very strange. I am seeing the same behavior. (I have LV 8.2)
When I first downloaded the VI, it opened just fine. If I did a saveas, closed the VI, and reopened the copy, I got 99% CPU usage. I reopened the one from the message, no problem. I left that one open and tried opening the one I had saved. It said I already had one in memory by that name do I want to view the one in memory or replace? I said replace. When it opened to the block diagram, everything was okay. But when I clicked on the window to view the front panel, that is when the CPU usage jumped up again.
So somehow the problem is associated with the FP. Nothing looks particular wrong about your code. The question is how did you manage to get a copy of the file that isn't causing problems when you open it?
I think you will want to recreate the VI from scratch. You are able to view a copy to see whay you have which is good. And it doesn't look too complicated.
What is interesting is that if I delete everything from the VI's block diagram (leaving nothing apparent on the FP), save, close, reopen, I still get the extreme CPU Usage. It seems confined to LV, as I am still able to switch over and working within the browser to answer this message.
Message Edited by Ravens Fan on 04-16-2007 02:30 PM

Gnome-open starts /bin/bash -ic (uname) and uses 100% CPU to open gvim

I've posted this on stackoverflow and got no answer, hopefully some archers can help me out:
When I execute
gnome-open textfile
I expect gvim to open up. Instead what happens is that the command hangs. When I check htop I see:
/bin/bash -ic (uname) > /tmp/{some random string of characters}
using 100% of the CPU. When I kill the process (and I have to use -9), then cpu usage goes back to normal and gvim opens.
Running
gvim -f textfile
without gnome-open works perfectly.
Any ideas where this process is coming from? Or what it's even doing?
/bin/bash -ic (uname)
doesn't even run for me.
Thank you!

I've posted this on stackoverflow and got no answer, hopefully some archers can help me out:
When I execute
gnome-open textfile
I expect gvim to open up. Instead what happens is that the command hangs. When I check htop I see:
/bin/bash -ic (uname) > /tmp/{some random string of characters}
using 100% of the CPU. When I kill the process (and I have to use -9), then cpu usage goes back to normal and gvim opens.
Running
gvim -f textfile
without gnome-open works perfectly.
Any ideas where this process is coming from? Or what it's even doing?
/bin/bash -ic (uname)
doesn't even run for me.
Thank you!

Multi-select LOV's hang form and use 100% CPU power

Hello,
We are using Designer 6i (6.5.52.1.0) and Headstart 6.5
In one of our forms we are using 6 Multi-select LOV's.
When we click the Cancel or Ok button (included through QMS_MSEL_LOV_BUTTONS), or hit Enter query in one of the ML_... blocks the form hangs and starts using all the CPU-power. I've tested this locally (c/s) and through the web (iAS), same result...
I already rebuilt the LOV's but the problem isn't solved.
We've got other forms with one or two multi-select LOV's, and these work fine.
Has anyone experienced this behaviour before, and what is the cure?
Thanks in advance!
Wouter

Wouter,
If you are running against Solaris, you could be running into the following:
Headstart applications that run via webforms on a Sun Solaris application server, suffer again from bug 1985903. This bug was spotted and solved a time ago and seemed to be solved at next
releases of Forms 6i. Now, on Solaris the bug is introduced again.
Description
===========
1. When using a multi-select LOV (which is displayed in a modal dialog
window), you select the records you want, press OK, and the application exits.
2. When using a shuttle control to move records from left to right or vice
versa, you select the records you want, press '>' to move them, and the
application exits.
This occurs in Forms 6.0.8.13.0 and 6.0.8.14.1. It did NOT occur in prior
releases. This is some kind of forms bug.
Workaround
==========
For some reason the call to procedure renumber in qms$msel.process_records
causes the application to exit. If you copy the code from renumber to all the
places from which it is called, it works fine.
- open qmslib65.pll in Form Builder
- open package body qms$msel
- find procedure process_records and define a local variable l_recno of type
number.
- find local procedure renumber and copy the body of this procedure
(everything
after 'begin' and before 'exception').
- replace each call to 'renumber;' with the copied code.
A new version of qms$msel package body is available on iXchange for download.
See Headstart Oracle Designer 6i, Bugs and Fixes.
Hope this helps,
Marc Vahsen
Headstart Team
Oracle NL

Discoveryd process uses 100% CPU - Safari Can't find the server

Hello
Since upgrading to Yosemite, I lose connection to the internet 2 or 3 times a day. (Outlook goes offline at the same time)
This is with a wired connection. (Wi-Fi is turned off)
Safari gives me the "Safari Can't Find the Server" message.
Restarting the computer solves the issue temporarily.
While I'm unable to connect to the internet, Activity Monitor shows a process named "discoveryd" that uses 100% CPU.
Force quitting this process gives me back access to the internet instantly. Unfortunately, I suffered a kernel panic (auto restart) a few minutes after force quitting discoveryd. I'm not 100% sure those 2 are related but it would be an odd coincidence as I never experienced had a single kernel on that system. Haven't tried force quitting that process since.
I'm using this iMac in a work environment. (Connected to a windows file server and exchange)
This issue has been happening 2-3 times a day since the day I upgraded to Yosemite.
Any pointers on what could fix this issue ?
Thanks

Start time: 10:04:31 11/11/14
Model Identifier: iMac11,3
System Version: OS X 10.10 (14A389)
Kernel Version: Darwin 14.0.0
Time since boot: 1:39
SATA
 WDC WD1001FALS-40Y6A0
USB
 USB-PS/2 Optical Mouse (Logitech Inc.)
Diagnostic reports
 2014-10-30 Adobe InDesign CC 2014 hang
 2014-10-30 Adobe InDesign CS6 hang
 2014-10-30 Adobe InDesign CS6 crash
 2014-10-30 FileMaker Pro hang x5
 2014-10-30 Finder crash* x2
 2014-10-30 Finder hang
 2014-10-30 Microsoft Outlook hang
 2014-10-30 iTunes hang
 2014-10-31 Adobe InDesign CC 2014 hang
 2014-11-04 Adobe InDesign CC 2014 crash x2
 2014-11-04 Adobe InDesign CC 2014 hang
 2014-11-04 Adobe InDesign CS6 crash x2
 2014-11-04 Microsoft Excel hang
 2014-11-05 Adobe InDesign CS6 hang
 2014-11-05 FileMaker Pro hang
 2014-11-10 Adobe InDesign CC 2014 hang
 2014-11-10 FileMaker Pro hang
 2014-11-11 Adobe Illustrator hang
 * Code injection
Log
 Nov 5 08:25:33 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 5 10:07:01 process discoveryd[49] thread 1190 caught burning CPU! It used more than 50% CPU (Actual recent usage: 82%) over 180 seconds. thread lifetime cpu usage 91.907001 seconds, (77.250009 user, 14.656992 system) ledger info: balance: 90001960650 credit: 91780798965 debit: 1778838315 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 109240779280
 Nov 5 10:09:03 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 5 11:46:47 process discoveryd[49] thread 1256 caught burning CPU! It used more than 50% CPU (Actual recent usage: 99%) over 180 seconds. thread lifetime cpu usage 91.591946 seconds, (75.959886 user, 15.632060 system) ledger info: balance: 90000109700 credit: 91486467544 debit: 1486357844 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 90105095085
 Nov 5 11:54:53 PM notification timeout (pid 275, Creative Cloud)
 Nov 5 11:54:53 PM notification timeout (pid 344, Adobe CEF Helper)
 Nov 5 11:54:53 PM notification timeout (pid 343, Adobe CEF Helper)
 Nov 5 12:35:03 jnl: b(1, 2): replay_journal: from: 57934848 to: 61127168 (joffset 0x1721c000)
 Nov 5 12:35:03 jnl: b(1, 2): journal replay done.
 Nov 5 12:38:37 jnl: b(1, 2): replay_journal: from: 61127168 to: 67488768 (joffset 0x1721c000)
 Nov 5 12:38:37 jnl: b(1, 2): journal replay done.
 Nov 5 12:38:40 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 5 13:26:28 process mdworker32[357] thread 8766 caught burning CPU! It used more than 85% CPU (Actual recent usage: 86%) over 40 seconds. thread lifetime cpu usage 81.048638 seconds, (76.580865 user, 4.467773 system) ledger info: balance: 34001309838 credit: 80940733771 debit: 46939423933 limit: 34000000000 (85%) period: 40000000000 time since last refill (ns): 39339579198 [fatal violation]
 Nov 5 14:26:53 PM notification timeout (pid 231, Creative Cloud)
 Nov 5 14:26:53 PM notification timeout (pid 325, Adobe CEF Helper)
 Nov 5 14:26:53 PM notification timeout (pid 326, Adobe CEF Helper)
 Nov 5 14:45:49 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 5 14:45:49 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 5 14:47:27 process discoveryd[49] thread 1023 caught burning CPU! It used more than 50% CPU (Actual recent usage: 99%) over 180 seconds. thread lifetime cpu usage 91.572722 seconds, (77.540749 user, 14.031973 system) ledger info: balance: 90015163759 credit: 91483527972 debit: 1468364213 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 90121915160
 Nov 5 15:13:33 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 6 08:25:36 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 6 11:59:36 PM notification timeout (pid 286, Creative Cloud)
 Nov 6 11:59:36 PM notification timeout (pid 355, Adobe CEF Helper)
 Nov 6 11:59:36 PM notification timeout (pid 356, Adobe CEF Helper)
 Nov 6 12:29:24 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 6 12:29:24 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 6 12:29:24 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 6 12:29:24 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 6 12:29:24 smbsmb2_sm2_b_parse_smchabnge_no_tipfary: ssmb_er_chq_replya failngeed_n ot6if0
 Nov 6 12:29:24 y: smb_rq_reply failed 60
 Nov 6 12:29:24 smb2_ssmmb2_b_spmabr_sparsee_c_hancgeh_naotinfgy: smb_rq_re_epnlyoti failfedy :60 sm
 Nov 6 12:29:24 b_rq_reply failed 60
 Nov 6 12:29:24 rs failed Qsmumber2b_sy m_Inrqfbo __pa60rr
 Nov 6 12:29:24 rse_change_notify: smb_rq_reply failed 60
 Nov 6 12:29:24 ply failed 60smb2_smb_parse_change
 Nov 6 12:29:24 _notify: smsmb_rq_reply failb2_ed smb_6parse_0
 Nov 6 12:29:24 ply failed smb2_smb_pa60
 Nov 6 12:29:24 rse_change_nsmb2otif_smy:b_ spmb_rq_reply failedars e_c60han
 Nov 6 12:29:24 ge_notify: smb_smb2_smb_parse_chrqange__repnotify: smb_rly fq_ailed reply failed 60
 Nov 6 12:29:24 smb2_smb_parssmb2_e_smbchange_pa_nrsote_chifany:ge _nosmb_tifrq_y:re smplb_y rq_fareilply failed 60
 Nov 6 12:29:24 y failed 60
 Nov 6 12:29:24 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 6 12:29:24 q_reply failed 60
 Nov 6 12:29:24 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 6 12:29:24 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 6 12:29:24 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 6 14:01:02 process discoveryd[49] thread 1259 caught burning CPU!; EXC_RESOURCE supressed due to audio playback
 Nov 6 15:49:49 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 6 16:10:23 process Adobe InDesign C[435] caught causing excessive wakeups. Observed wakeups rate (per sec): 309; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45011
 Nov 7 08:25:38 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 10 09:28:46 process discoveryd[49] thread 1195 caught burning CPU! It used more than 50% CPU (Actual recent usage: 99%) over 180 seconds. thread lifetime cpu usage 152.284113 seconds, (127.648543 user, 24.635570 system) ledger info: balance: 90002963251 credit: 152063056684 debit: 62060093433 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 90142287445
 Nov 10 09:42:09 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 10 11:20:45 process discoveryd[49] thread 1182 caught burning CPU! It used more than 50% CPU (Actual recent usage: 99%) over 180 seconds. thread lifetime cpu usage 150.526060 seconds, (126.552866 user, 23.973194 system) ledger info: balance: 90000111985 credit: 150369654672 debit: 60369542687 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 90164134478
 Nov 10 12:14:06 PM notification timeout (pid 261, Creative Cloud)
 Nov 10 12:14:06 PM notification timeout (pid 332, Adobe CEF Helper)
 Nov 10 12:14:06 PM notification timeout (pid 333, Adobe CEF Helper)
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 y failed 60
 Nov 10 12:43:27 failed mb60
 Nov 10 12:43:27 smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:43:27 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 12:46:06 process WindowServer[121] caught causing excessive wakeups. EXC_RESOURCE supressed due to audio playback
 Nov 10 12:49:29 jnl: b(1, 2): replay_journal: from: 27704832 to: 35355648 (joffset 0x1721c000)
 Nov 10 12:49:29 jnl: b(1, 2): journal replay done.
 Nov 10 12:54:05 jnl: b(1, 2): replay_journal: from: 35355648 to: 40313344 (joffset 0x1721c000)
 Nov 10 12:54:05 jnl: b(1, 2): journal replay done.
 Nov 10 12:54:08 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 10 14:31:43 PM notification timeout (pid 232, Creative Cloud)
 Nov 10 14:31:43 PM notification timeout (pid 327, Adobe CEF Helper)
 Nov 10 14:31:43 PM notification timeout (pid 324, Adobe CEF Helper)
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 : smb_rq_reply failesmbd 2_smb_60
 Nov 10 15:07:47 parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 tify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_nsotify:mb2 sm_b_rq_reply sfailmed b60
 Nov 10 15:07:47 _parse_change_notify: smbsmb2_rq__rsepmb_parsly failee_d ch60ange_notify
 Nov 10 15:07:47 : smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:47:46 process discoveryd[49] thread 1013 caught burning CPU! It used more than 50% CPU (Actual recent usage: 99%) over 180 seconds. thread lifetime cpu usage 153.503446 seconds, (128.774521 user, 24.728925 system) ledger info: balance: 90007455004 credit: 153327303891 debit: 63319848887 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 90099512937
 Nov 11 08:25:38 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 11 09:38:05 process Adobe InDesign C[553] caught causing excessive wakeups. Observed wakeups rate (per sec): 283; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45017
 Nov 10 14:31:43 PM notification timeout (pid 327, Adobe CEF Helper)
 Nov 10 14:31:43 PM notification timeout (pid 324, Adobe CEF Helper)
 Nov 10 14:31:43 com.apple.dpd: Service exited with abnormal code: 75
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 : smb_rq_reply failesmbd 2_smb_60
 Nov 10 15:07:47 parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 tify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_nsotify:mb2 sm_b_rq_reply sfailmed b60
 Nov 10 15:07:47 _parse_change_notify: smbsmb2_rq__rsepmb_parsly failee_d ch60ange_notify
 Nov 10 15:07:47 : smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:07:47 smb2_smb_parse_change_notify: smb_rq_reply failed 60
 Nov 10 15:47:46 process discoveryd[49] thread 1013 caught burning CPU! It used more than 50% CPU (Actual recent usage: 99%) over 180 seconds. thread lifetime cpu usage 153.503446 seconds, (128.774521 user, 24.728925 system) ledger info: balance: 90007455004 credit: 153327303891 debit: 63319848887 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 90099512937
 Nov 10 16:47:01 com.apple.WebKit.Networking.UUID: Service exited with abnormal code: 1
 Nov 11 08:25:37 com.apple.Kerberos.kdc: Service exited with abnormal code: 1
 Nov 11 08:25:38 ** GPU Hardware VM is disabled (multispace: disabled, page table updates with DMA: disabled)
 Nov 11 08:56:36 com.apple.dpd: Service exited with abnormal code: 75
 Nov 11 09:38:05 process Adobe InDesign C[553] caught causing excessive wakeups. Observed wakeups rate (per sec): 283; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45017
CPU per process: com.apple.WebKit (UID 501) is using 41.2 %
Daemons
 com.apple.installer.osmessagetracing
 com.microsoft.office.licensing.helper
 com.adobe.fpsaud
Agents
 com.adobe.CS4ServiceManager
 com.adobe.AdobeCreativeCloud
 com.adobe.ARM.UUID
 com.adobe.ARM.UUID
 com.apple.Safari
 com.adobe.ARM.UUID
 com.google.keystone.user.agent
 com.apple.AirPortBaseStationAgent
App extensions
 com.apple.InternalFiltersXPC
Contents of /Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist (checksum 461455494)
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
 <key>Label</key>
 <string>com.adobe.AdobeCreativeCloud</string>
 <key>Program</key>
 <string>/Applications/Utilities/Adobe Creative Cloud/ACC/Creative Cloud.app/Contents/MacOS/Creative Cloud</string>
 <key>ProgramArguments</key>
 <array>
 <string>/Applications/Utilities/Adobe Creative Cloud/ACC/Creative Cloud.app/Contents/MacOS/Creative Cloud</string>
 <string>--showwindow=false</string>
 <string>--onOSstartup=true</string>
 </array>
 <key>RunAtLoad</key>
 <true/>
 </dict>
 </plist>
Contents of Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist (checksum 4071182229)
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
 <key>Label</key>
 <string>com.adobe.AAM.Scheduler-1.0</string>
 <key>Program</key>
 <string>/Library/Application Support/Adobe/OOBE/PDApp/UWA/UpdaterStartupUtility</string>
 <key>ProgramArguments</key>
 <array>
 <string>/Library/Application Support/Adobe/OOBE/PDApp/UWA/UpdaterStartupUtility</string>
 <string>-mode=scheduled</string>
 </array>
 <key>StartCalendarInterval</key>
 <dict>
 <key>Minute</key>
 <integer>0</integer>
 <key>Hour</key>
 <integer>2</integer>
 </dict>
 </dict>
 </plist>
Contents of Library/LaunchAgents/com.adobe.ARM.UUID.plist (checksum 394026997)
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
 <key>Label</key>
 <string>com.adobe.ARM.UUID</string>
 <key>ProgramArguments</key>
 <array>
 <string>/Applications/Adobe Reader.app/Contents/MacOS/Updater/Adobe Reader Updater Helper.app/Contents/MacOS/Adobe Reader Updater Helper</string>
 <string>semi-auto</string>
 </array>
 <key>RunAtLoad</key>
 <true/>
 <key>StartInterval</key>
 <integer>12600</integer>
 </dict>
 </plist>
Contents of Library/LaunchAgents/com.adobe.ARM.UUID.plist (checksum 4116814193)
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
 <key>Label</key>
 <string>com.adobe.ARM.UUID</string>
 <key>ProgramArguments</key>
 <array>
 <string>/Applications/Adobe Acrobat XI Pro/Adobe Acrobat Pro.app/Contents/MacOS/Updater/Adobe Acrobat Updater Helper.app/Contents/MacOS/Adobe Acrobat Updater Helper</string>
 <string>semi-auto</string>
 </array>
 <key>RunAtLoad</key>
 <true/>
 <key>StartInterval</key>
 <integer>12600</integer>
 </dict>
 </plist>
Contents of Library/LaunchAgents/com.adobe.ARM.UUID.plist (checksum 926752576)
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
 <key>Label</key>
 <string>com.adobe.ARM.UUID</string>
 <key>ProgramArguments</key>
 <array>
 <string>/Applications/Adobe Acrobat X Pro/Adobe Acrobat Pro.app/Contents/MacOS/Updater/Adobe Acrobat Updater Helper.app/Contents/MacOS/Adobe Acrobat Updater Helper</string>
 </array>
 <key>RunAtLoad</key>
 <true/>
 <key>StartInterval</key>
 <integer>12600</integer>
 </dict>
 </plist>
Contents of Library/LaunchAgents/com.apple.SafariBookmarksSyncer.plist (checksum 4209634474)
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
 <key>Label</key>
 <string>com.apple.Safari</string>
 <key>LimitLoadToSessionType</key>
 <string>Aqua</string>
 <key>ProgramArguments</key>
 <array>
 <string>/Applications/Safari.app/Contents/SafariSyncClient.app/Contents/MacOS/S afariSyncClient</string>
 <string>--sync</string>
 <string>com.apple.Safari</string>
 <string>--entitynames</string>
 <string>com.apple.bookmarks.Bookmark,com.apple.bookmarks.Folder</string>
 </array>
 <key>RunAtLoad</key>
 <false/>
 <key>ThrottleInterval</key>
 <integer>60</integer>
 <key>WatchPaths</key>
 <array>
 <string>/Users/USER/Library/Safari/Bookmarks.plist</string>
 </array>
 </dict>
 ...and 1 more line(s)
Contents of Library/LaunchAgents/com.google.keystone.agent.plist (checksum 64800286)
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
 <key>Label</key>
 <string>com.google.keystone.user.agent</string>
 <key>LimitLoadToSessionType</key>
 <string>Aqua</string>
 <key>ProgramArguments</key>
 <array>
 <string>/Users/USER/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bu ndle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftw areUpdateAgent</string>
 <string>-runMode</string>
 <string>ifneeded</string>
 </array>
 <key>RunAtLoad</key>
 <true/>
 <key>StartInterval</key>
 <integer>3523</integer>
 <key>StandardErrorPath</key>
 <string>/dev/null</string>
 <key>StandardOutPath</key>
 <string>/dev/null</string>
 </dict>
 </plist>
Bad plists
 Library/Preferences/com.apple.iphotomosaic.plist
Listeners
 launchd: afpovertcp
 launchd: afpovertcp
 launchd: microsoft-ds
 launchd: ssh
 launchd: microsoft-ds
 launchd: ssh
 kdc: kerberos
User login items
 Microsoft Outlook
 - /Applications/Microsoft Office 2011/Microsoft Outlook.app
 TransmitMenu
 - /Applications/Transmit.app/Contents/MacOS/TransmitMenu.app
 ClipMenu
 - /Applications/ClipMenu.app
 Dept
 - /Volumes/Dept
 Public
 - /Volumes/Public
 Apps
 - /Volumes/Apps
Restricted files: 4584
Lockfiles: 99
Elapsed time (s): 352

Finder and loginwindow use 100% cpu with 10.6.8

I recently installed the patch to OS X 10.6.8 and now the finder is very unstable and uses 100% cpu and the loginwindow uses 100% cpu also. Yes I have Parallels 6 on this machine but I already "un-checked" the "show windows applications in doc" option which is the recommended solution. However, this did not fix the problem. I do not know how to determine what actual process is causing this finder / loginwindow issue. I very much appreciate if anyone has suggestion how to fix this problem.
This is on a mid-2011 MacBookPro.
thank you.

TBauer, I had the same problem with 10.6.8 using 100% of the CPU with Parallels 6 installed. The following steps solved this problem for me:
0. Take a screen shot of your Dock if you wish to remember it as currently set
1. Launch Activity Monitor and click on the CPU column so you can see Dock using the CPU
2. Move ///Users/ ... /Library/Preferences/com.apple.dock.plist to the trash
3. Click on Dock and click on Quit Process to stop the Dock
OS X will then rebuild the default Dock
4. Put the items back in the Dock that you want
That solved the problem for me yesterday morning. I've launched Parallels 6 several times now and moved the machine from my work network to home and the 100% CPU problem hasn't returned.
Hope that works for you, too!
I don't think using the combo updater will solve the problem. The problem appears to be a .plist that is generated with OS X 10.6.7 and earlier that contains icons of a larger than Apple documented size causes the CPU looping. Rebuilding the dock.plist under OS X 10.6.8 appears to solve the problem.
Parallels has issued a knowledge bulletin saying they are looking into the problem. On their web site they have another approach involving moving the offending icon out of the dock to solve the problem. I like my solution better but theirs works, too.

Client process (uniengd) on the Calendar server is consuming 100% CPU usage

The Calendar client bits in the Communicator 4.5 release (Calendar Build 981008)
are suspect of hanging the Calendar server when the end user uses the off-line
feature. The behavior seen will be that a cpu will start climbing and could
reach 80-100% of usage, which will cause the response time for all other end
users to be extremely slow and may not even accept any new logins.

The patch for these bits is available via the Smart Update (Windows and Mac) web
site:

http://home.netscape.com/smartupdate/su1_40.html
 Or you can download the complete version from
http://home.netscape.com/download/selectplatform_1_361.html

For Unix platforms, you will need to download the compressed tar file
(available from http://help/filelib.html#nscal)
and reinstall it.
NOTE: To verify that you are executing a patched version, in the
Calendar client:
Windows platform
 Help menu pulldown, About Netscape Calendar, make sure it has Build
981104 or higher.
 Mac platform
 Select the file from your desktop
 File menu pulldown, Get Info. Make sure has a date of 121698, version
4.51 or later.
 Unix platform
 Help menu pulldown, About Netscape Calendar, make sure it has is Version
4.51 or higher

The procedure for determining which user of Calendar is causing the server's cpu
hang is as follows:
<OL>
<LI>Using your favorite monitoring tool on the server, note the PID
 (process ID) of the uniengd process that is consuming
80 - 100% cpu activity.
<LI>Change directory to /users/unision/db/tmp/PID#
<LI>Execute the command "strings" on all the files in the directory
 (there are usually not very many):

 # strings *

 Near the end of the output, you will see the user's name.
<LI>You can now kill the uniengd process on the server:

 # kill PID# (note: do not use the kill -9 unless absolutely
 necessary!)

<LI>Contact the name of the user whose process you looked up and determine
 what version of Calendar client they are using. Immediately inform
 them of your procedure on upgrading to the correct version.
</OL>

Hi TrondWH,
Thanks for contacting Microsoft.
Currently, would you please try cleaning boot the server and test how the issue goes. Cleaning boot can exclude some third-party application affect. Following are the detailed steps about clean boot:
Log on to the computer by using an account that has administrator rights.
Click Start, type msconfig.exe in the Start Search box, and then press ENTER to start the
 System Configuration Utility.
On the General tab, click Selective Startup, and then click to clear the Load startup items check box. (The Use Original Boot.ini check box is unavailable.)
On the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all.
Click OK, Choose Don’t show this message again and then click Restart.
Please check if the issue is still the same.
Please let me know the result.
Best regards,
Sophia Sun
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Coreservicesd 100% cpu on 10.6 and quicksilver

I've been suffering from teh 100% coreservicesd race condition for a while. I've searched around for a long time before finding a discussion thread that hinted at the issue I'm having - quicksilver.
The problem was with the 'Dock' being in one of the 'Catalogue' items.
1. right click on quicksilver menu icon
2. select 'Catalog'
3. select 'User'
4. uncheck 'Dock'
As soon as I did this, coreservicesd cpu usage immediately dropped.

TBauer, I had the same problem with 10.6.8 using 100% of the CPU with Parallels 6 installed. The following steps solved this problem for me:
0. Take a screen shot of your Dock if you wish to remember it as currently set
1. Launch Activity Monitor and click on the CPU column so you can see Dock using the CPU
2. Move ///Users/ ... /Library/Preferences/com.apple.dock.plist to the trash
3. Click on Dock and click on Quit Process to stop the Dock
OS X will then rebuild the default Dock
4. Put the items back in the Dock that you want
That solved the problem for me yesterday morning. I've launched Parallels 6 several times now and moved the machine from my work network to home and the 100% CPU problem hasn't returned.
Hope that works for you, too!
I don't think using the combo updater will solve the problem. The problem appears to be a .plist that is generated with OS X 10.6.7 and earlier that contains icons of a larger than Apple documented size causes the CPU looping. Rebuilding the dock.plist under OS X 10.6.8 appears to solve the problem.
Parallels has issued a knowledge bulletin saying they are looking into the problem. On their web site they have another approach involving moving the offending icon out of the dock to solve the problem. I like my solution better but theirs works, too.

Instense hd activity and 100%cpu make my system completely unsable

hi.
it happenned the first time with some app (i don't know which one) using the hard disk quite intensively.
and then i couldn't even move my mouse. well i move it but 10 seconds later the pointer move on the screen. and i coudn't do anything under X. even type something.
i manage to go to a console via CTRL-ALT-F1. but couldn't login because login give me a time-out ! and then i finally rebooted so i could get back my system and use it.
then,later, i decided to run dd if=/dev/urandom of=/somepartition bs=1024 before setting up a crypted partition. and it happened again !
the hard-disk activity and the 100% CPU usage . and i couldn't do again anything except reboot !!
when i run the same dd command on my Arch 32 bits. it does give 100% CPU usage too but i can still use X without problem. even without any slow down.
so the 32bits system is an old Athlon XP 1800+ with an IDE disk.
and the Arch64 is a brand new Athlon 64 X2 4400+ with a SATA drive and a nforce chipset MCP61.
so what is the cause of that ? clearly the cpu is so used that nothing could work. but on the 32bits system too. and it still works. so ?
is the configuration of the kernel of arch64 different from arch32 ?
i am thinking at compiling my own kernel with PREEMT configured or even compiled an rt kernel. but why is this needed whereas on the 32bit arch all is fine ???

may be that's bs=1024 the problem and what that caused the slowdown ?
or may be i mistyped /dev/urandom and used /dev/random ?
i am using now :
schedtool -B -e dd if=/dev/urandom of=/somepartition
and it works nice. no more than 50% CPu usage. and no slowdown...
the schedtool -B is to be sure there will be no freeze and that dd will not take all the cpu power...

Dock frozen, taking 100% CPU, 50gb swap

My dock is frozen and shows 100% cpu use (that is, 100% of one core). It gradually takes more and more memory until I run out of hard disk space. Killing the process does nothing - it immediately comes back at 100% of cpu and starts eating the memory over again. Same with deleting com.apple.dock.plist.
This problem was occuring in 10.8.3, so i tried updating to 10.8.4, which had no effect.
Any ideas?

I had this problem, eventually found a solution - it's to do with Parallels (and maybe VMWare Fusion) sharing Windows applications to the Mac Dock. It turned out that I had quit Parallels, but somehow it had left something about these shared Dock items in limbo. Restarting Parallels got things right again, then disabling the Shared Windows Apps in the configuration of the VMs
See http://reviews.cnet.com/8301-13727_7-20074173-263/dock-using-100-cpu-after-os-x- 10.6.8-update-for-parallels-6-users/

"du process" pops up and occupy 100% CPU

Similar Messages

Maybe you are looking for