Sandboxd using high amount of CPU Because of WIFI

Question

Level 1

0 points

Sandboxd using high amount of CPU Because of WIFI

Hello everyone!

I noticed on this last days that my fans were doing a lot of noise, like if some heavy program was in use.

The thing is, im not running anything and on my activity monitor i see a sandboxd from the root using 45% of my cpu ( i got a macbook pro 15' early 2011 i7 2.2ghz ), and the "father" of that process is launchd.

Thing is, if i turn my wifi off, that process goes away and my mac will go to the normal 1% usage, but if i turn my wifi on, thats it, i see that same process comming again :/

Any clue about this problem? I really need a hand guys.

Im using mountain Lion 10.8.3.

Thanks you a lot in advance!

MacBook Pro, OS X Mountain Lion (10.8.2)

Posted on Apr 29, 2013 6:07 AM

Reply

Answer 1

RuiLeao Author

Level 1

0 points

Apr 29, 2013 6:11 AM in response to RuiLeao

If it helps:

Analysis of sampling sandboxd (pid 379) every 1 millisecond

Process: sandboxd [379]

Path: /usr/libexec/sandboxd

Load Address: 0x108e81000

Identifier: sandboxd

Version: ??? (???)

Code Type: X86-64 (Native)

Parent Process: launchd [1]

Date/Time: 2013-04-29 14:10:18.864 +0100

OS Version: Mac OS X 10.8.3 (12D78)

Report Version: 7

Reply

Answer 2

RuiLeao Author

Level 1

0 points

Apr 29, 2013 6:24 AM in response to RuiLeao

Ok, i just found it out by luck!

It was happening cuz of an app that i installed on the other day, called "Wireless signal" ! It was pretty usefull, but it takes a lot of your CPU, so dont use it guys. ( tood it from app store ).

Thanks anyway ,hf

Reply

Answer 3

erkwok

Level 1

0 points

Jul 28, 2013 8:11 AM in response to RuiLeao

Thanks for putting this post.

I have exactly the same problem. The wireless signal apps cost me 40%+ cpu to sandboxd. When I close the app, the sandboxd drops down to 0.1%

Is there anyway to know the which app is causing highcpu to sandbox?

Just in case the problem comes back with other apps, I know how to troubleshoot.

Reply