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

Bash causes high CPU

I'm monitoring the status of my MacBook Pro using iStat, and every hour (or so) my CPU usage shoots up to 100%.


When I view my Acitvity Monitor, there is not one process that appears to be have a very high CPU, even though iStat shows my CPU usage go up to 100% (and the noise of the fan begins).


However, I have found that the process called "bash" is always either top or 2nd to the top of the list of CPU usage, even though itself is around 8-10%.


I have tried shutting down a number of the processes and they have no effect on the 100% CPU usage, except for "bash". When I Force Quit bash, the CPU usage drops off back to a very low value immediately.


As such, I was wondering what may be causing "bash" to cause 100% CPU usage, and how I may resolve this.


Many thanks!



D.

MacBook Pro, Mac OS X (10.6.8)

Posted on Jul 6, 2011 3:37 AM

Reply
18 replies

Jul 7, 2011 1:48 AM in response to docgecko

Just to pass on a bit of information:


I found another similar question on these forums about a potential issue relating to a job being stuck in the printer queue, like a rougue job. If you access the printer queue via http://localhost:631/jobs/ you can cancel the rouge job.


Cancelling the job actually cut down considerably the number of times per day my mac CPU went up to 100%. It still happens but with longer durations between. So its possible that it is still an issue related to the printer software. Btw, I am using a Brother MFC-845CW.


If anyone has any other potential solutions, I'd love to hear them.


Many thanks,


D.

Jul 30, 2012 5:23 PM in response to docgecko

OMG!!! Thank you, thank you, thank you! That's all I can say. This issue was driving me crazy. I just upgraded to Mountain Lion with the other 3 million folks and all of sudden, my MacBook Pro was heating up and the RPMs were off the grid. Couldn't figure out why. Before this, I almost never heard the fans going on (I know they run all the time) but the between the fan and the RPMs I was getting up to 4500 with nothing open and the temp was going back and forth between 85 to 90 degrees. Needless to say, I was somewhat concerned.


I have been on the Internet for about 2 days trying to figure this out. I know that the computer was indexing after the upgrade but just could not find the source of the RPM problem. Found lots of info about re-setting the SMC, but didn't try that yet. This was going to be my last resort. Downloaded SMC Fan Control and that helped somewhat. Erased Sophos Anti-Virus which had Intercheck running and taxing my CPU. Then I stumbled upon this particular thread and lo and behold - I had downloaded Send to Kindle. I had noticed in the Activity Monitor that this "bash" process was running but didn't pay much attention because the CPU was at around 7 - 8%, not 99% of the CPU which would be obvious. Decided it couldn't hurt to remove this app and the next thing I know my temp dropped down to 49 degress and the RPMs are at 2500 and NO FANS running like crazy.


I just can't thank you all enough for this extremely valuable information - I hope Amazon fixes this. I really loved Send to Kindle app but I love my MacBook Pro more so the choice was simple. So glad I found this forum.

Jul 31, 2012 12:19 AM in response to docgecko

I'm glad that it helped. It has been a long serch for me too and trust me that your thanks are the perfect reward for the time spent searching.


Amazon sent me official conclusion today:


"We have researched on this issue and got to conclusion that during the backup/restore process, /var/spool/stkPrinter/ and its files are lost, causing the dependent script stkLaunchAgent.sh to spike the CPU usage.


STK uses a communication pipe present in (/private/var/spool/stkPrinter/$USER/stkPipe) to communicate the printed file name to the STK app. STK Printer backend writes on the pipe and a bash script(/usr/bin/stkLaunchAgent.sh) listens on the pipe in a loop. When the bash script starts, it checks whether the pipe is present and if not creates it.


This can be fixed by re-installing the app."


I tried to install Send to Kindle again... and it works! So Amazon guys fixed it...


Enjoy

Aug 2, 2012 9:35 PM in response to jollypants

So glad you were able to find this forum and more importantly, the solution to your problem. I agree it is such an odd issue. But all the THANKS goes to docgecko for putting the question out there and Fieldman for the solution. These forums are invaluable and if like me, the issue was driving you nuts, it is such a relief to find a "true" solution to an issue. Glad to hear things are now back to normal.


FYI - if you notice Fieldman's post from 7/31, you'll see he was notified that the issue has been fixed by Amazon and Send to Kindle is good to go now. I re-downloaded Send to Kindle and so far, I have had no issues with the application. Good Luck!

Aug 3, 2012 7:33 AM in response to Bob Kujda

Neither could I. I had to change the settings in the security preferences. I fear this aspect of the security of ML is taking developers a bit by suprise.


There are people out there who have been paying attention and disagree, and to you fine folks I *bow*. For the rest of the dev. community who missed it.. we'll just have to use the same discression (as users) we did before we upgraded or began using ML.


I think if you trusted it (developer, or co creating said app) before the upgrade, you should be able to trust it now right?

Bash causes high CPU

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.