Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question already has an answer here:

I am using OSX 10.7.5 and my OSX is becoming a bit unresponsive, comparing to what it was like before. Sometimes just opening new window of browser or terminal takes few seconds or the Dock hovering effect is not fluent. At these moments I watch system resources and I still have 3G of memory free and the processor is not used at all. Can it be caused by hard drive or other IO? How can I found out which application is causing this?

share|improve this question

marked as duplicate by Ƭᴇcʜιᴇ007, Tog, Brad Patton, davidgo, terdon Apr 29 '13 at 4:16

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Do you have some virus scanner enabled. – Buscar웃 Apr 28 '13 at 11:19
How is your widowserver doing ? – Buscar웃 Apr 28 '13 at 11:27
No, I don't have any virus scanner. Windowserver seems to be having no troubles. But I would prefer to see some real statistics of what is blocking the system. – Vojtěch Apr 28 '13 at 12:08
You are not telling us the full story. Giving comments to answers like "I tried this" is not helpful. So please elaborate in your OP what have you tried and if you are only looking for a very specific solution. – Buscar웃 Apr 28 '13 at 13:53

Use top to monitor system resources. As you mention issues with opening the browser possibly there is malware active or some other agent which is causing unwarranted network activity. To monitor this use-:

ifconfig -a  # for the network interface name to monitor


tcpdump -i <interface>

An alternative for network monitoring is nettop - a command line tool which I believe is available from Lion version. It's available from Apple store.

share|improve this answer
Of course I have tried top, but it seems that hardly any system resources are used. Will try the tcpdump. – Vojtěch Apr 28 '13 at 12:37

Check the logs for clues. Even a high volume of relatively harmless error messages (itself an error!), could swamp your response time.

Edit: /var/log/system.log and /var/log/kernel.log would be most likely. Or open the Console app in Utilities and show all messages.

share|improve this answer
Which logs? There are many of them on OSX. – Vojtěch Apr 28 '13 at 12:38
(See my edit..) – JRobert Apr 28 '13 at 14:44

Not the answer you're looking for? Browse other questions tagged .