what is airportd and why is it using 100% CPU?

{quote:title=Gozar wrote:}
I'm seeing this too on my Macbook, right after the 10.5.3 update. Quitting it with Activity Monitor seems to bring things back to normal.{quote}

Yes, but.

Then when it comes back on, it does the same thing. However, I seem to have fixed it as follows:

System Preferences>Network
Choose Airport, and "Advanced"
I unticked "remember any network this computer has joined" and I also removed some networks from the list. Since then, all is OK.

Hope this works for others.

-j

Would there be a reason why this screwyness only became evident after the update?

Here is the result of sampling the process, FYI:


Sampling process 27135 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols...
Analysis of sampling airportd (pid 27135) every 1 millisecond
Call graph:
2200 Thread_2503
2200 0x1e8e
2200 0x5826
2200 mach msgserver
2200 mach_msg
2200 mach msgtrap
2200 mach msgtrap
2200 Thread_2603
2200 thread_start
2200 pthreadstart
2200 0x4d0e
2200 pthread condtimedwait$UNIX2003
2200 _semwaitsignal
2200 _semwaitsignal
2200 Thread_2703
2200 thread_start
2200 pthreadstart
2200 0x4ba9
2200 CFRunLoopRun
2200 CFRunLoopRunSpecific
2200 mach_msg
2200 mach msgtrap
2200 mach msgtrap
2200 Thread_2803
2200 thread_start
2200 pthreadstart
2200 0x77e4
2200 objc_msgSend
2200 objc_msgSend

Total number in stack (recursive counted multiple, when >=5):

Sort by top of stack, same collapsed (when >= 5):
mach msgtrap 4400
_semwaitsignal 2200
objc_msgSend 2200
Sample analysis of process 27135 written to file /dev/stdout