Site acting odd: requiring double clicks, etc

Malware, virus, or browser issue?

[GoNC]

For about a week now, I've noticed an intermittent problem on my site. I can mouse over links, and the cursor doesn't change. Sometimes I can click and it connects, but sometimes it requires a double-click.

And sometimes, I'll mouse over a link and the cursor changes to a hand, but then when I leave the link the hand stays indefinitely.

Other users have mentioned the same problem, and I've seen it myself in both Firefox and Chrome. One user said they are seeing it in IE, but I haven't confirmed that for myself.

A scan of the server with ClamAV and rkhunter both say I'm clean. I'm not seeing this on other sites, though, so I'm almost convinced the problem is on the server. But I'm not getting any errors, just oddness with the cursor.

Any suggestions at all would be appreciated! TIA.

[martinibuster]

Sounds like a lot of things downloading and something hanging. Added any new scripts?

[not2easy]

Possibly related - I see a lot of people talking about Google's spidering "going ballistic" over in the Google SERPs discussion: [webmasterworld.com...] so you might want to check your logs or stats to see if they are busier than usual at the times corresponding to your issue? I have seen them when they go into that mode and it is incredible the number of files they will grab in one session and using multiple spiders concurrently. I don't know how anyone else can use a site when they do that.

[GoNC]

I haven't changed anything on the site in a few months, really. I did have an unexplained server crash last week, though (usage was normal, then it just went down and I had to reboot), and I don't remember seeing this before that.

not2easy, I checked Google's Webmaster Tools, and it doesn't look like Google is doing anything major... which is actually a different problem (stay tuned for a second thread)! The "Crawl Stats" only shows them using a max of 102kb in the last 90 days.

Back to the topic of the thread, though, I was seeing this issue when I posted early this morning, and I'm still seeing it now. It seems to be domain-specific, though; when I access using a parked domain, I don't have the same problem.