Anyone know what this is......

[spencecb]

I just opened up Activity Monitor on my MacBook Pro and there is a process running called "blued." It is running under root, taking up 80-83% CPU time, 1 thread and 96 MB RAM.

Anyone know what the hell this is? I have Folding running on the two cores and nothing else is open.

Is this a system maintenence program? That is the only thing I can think of....

Any guesses/answers would be awesome!

 

[briangig]

pretty sure thats the bluetooth daemon. you using bluetooth mouse or kb?

 

[~Shard~]

I'm guessing blued is probably a Bluetooth Daemon process. I don't think it should be taking up that much CPU % though... As I don't have BT on my Mac, I'm afraid I can't be much more help.

 

[spencecb]

Yeah, that is exactly what it was. Bluetooth was acting funny yesterday when I used it. It was very unresponsive when clicking on the icon on the menu bar. I just force quit the process to get rid of it.

EDIT: And now, Bluetooth isn't working at all....****! Any ideas what to do about that??

 

[spencecb]

Okay, nevermind. A simple restart fixed the problem! Crisis averted!

 

[~Shard~]

Okay, nevermind. A simple restart fixed the problem! Crisis averted!

Good to hear! Hopefully it won't act up on you again.

 

[SmurfBoxMasta]

Okay, nevermind. A simple restart fixed the problem! Crisis averted!.

Inothawerdz........

restart 1st = Anti-SPAZZO

 

[sam10685]

Okay, nevermind. A simple restart fixed the problem! Crisis averted!

when in doubt, restart. (macs only)

 

[~Shard~]

when in doubt, restart. (macs only)

Actually, no, this applies to Windows machines as well in some cases, but for different reasons. Sometimes Windows is just so stupid, that even though restarting shouldn't fix the problem, it does. After all, it's the first suggestion made by 90% of Help Desk agents when people call in with problems on Windows machines...

 

[SmurfBoxMasta]

Sometimes Windows is just so stupid, that even though restarting shouldn't fix the problem, it does. After all, it's the first suggestion made by 90% of Help Desk agents when people call in with problems on Windows machines...

huummmm.......just goes to show ya how "smart" they both are

ie......Windblows & most of their "techies" haven't had a FRIGGIN clue since a clue had them !

 

[THX1139]

After all, it's the first suggestion made by 90% of Help Desk agents when people call in with problems on Windows machines...

That's interesting. I would have thought the first question they would ask is whether their computer was plugged in or not.

 

[~Shard~]

That's interesting. I would have thought the first question they would ask is whether their computer was plugged in or not.

That's the first question. The first suggestion is to reboot.

 

[sam10685]

Actually, no, this applies to Windows machines as well in some cases, but for different reasons. Sometimes Windows is just so stupid, that even though restarting shouldn't fix the problem, it does. After all, it's the first suggestion made by 90% of Help Desk agents when people call in with problems on Windows machines...

true, but my experience with both computers is this; restarting a mac will 99% of the time fix the problem... with a windows piece of junk, u will be very lucky if it fixes ur mishap.

 

[~Shard~]

true, but my experience with both computers is this; restarting a mac will 99% of the time fix the problem... with a windows piece of junk, u will be very lucky if it fixes ur mishap.

Quite true - there's always that element of "black magic" when it comes to Windows...

 

[/dev/toaster]

I have had my MBP for about a month now, and I have been forced to reboot it 2 times and pull the battery once.

First time was because World of Warcraft locked up. During login, if you lose your connection the game tends to hang. There isn't any timeout there, its very odd.

Second time was the same thing, except it was a hard lock. I couldn't even use the power button, was very annonying.

Third time was the other day. I was going to show someone photobooth, (Which I have running all day, due to that damn whine). It was minimized and wouldn't maximize. It just sat there using 80% of 1 core. (Odd it didn't use both cores, maybe its not multithreaded) Anyway, I tried to kill it and regardless of what I did, it wouldn't die. I even fired up the console in an attempt to kill it. During this time, the green light wasn't even on.

I hate it when the OS is damn stable for me all day, then when I go to show the system to someone it craps out.

 

[SmurfBoxMasta]

I hate it when the OS is damn stable for me all day, then when I go to show the system to someone it craps out.

Aint life a biatch

 

[trogdor!]

It amazing how many problems go away after a restart. It is the first rule of thumb in tech repair. haha.