Lion 10.7.1
Safari 5.1
I have been poking around a bit exploring resource utilization, and have come across a bit of an issue, wondering if anyone else notices it as well. I see the same on two machines, a 4+ year old MBP, and a newer iMac.
Running netstat, I am seeing Safari keep quite a few connections in the CLOSE_WAIT state, long after they should have been closed out (overnight, even, so long as Safari remains open). Most of these are with the 74.125.x.x block of IP's, which is Google. By tracking what I do, they mostly seem to originate from the Google search box use, but I have also seen other remote IP's. All are on ports 80 and 443.
Most of my total connections close on out as they should, considering how many I open, but a noticeable number of them remain in CLOSE_WAIT. After a couple hours using Safari, it is not unusual to see several dozen hung in CLOSE_WAIT.
The second you quit Safari, all of these CLOSE_WAIT's immediately move to the LAST_ACK state, and then close on out normally.
Safari 5.1
I have been poking around a bit exploring resource utilization, and have come across a bit of an issue, wondering if anyone else notices it as well. I see the same on two machines, a 4+ year old MBP, and a newer iMac.
Running netstat, I am seeing Safari keep quite a few connections in the CLOSE_WAIT state, long after they should have been closed out (overnight, even, so long as Safari remains open). Most of these are with the 74.125.x.x block of IP's, which is Google. By tracking what I do, they mostly seem to originate from the Google search box use, but I have also seen other remote IP's. All are on ports 80 and 443.
Most of my total connections close on out as they should, considering how many I open, but a noticeable number of them remain in CLOSE_WAIT. After a couple hours using Safari, it is not unusual to see several dozen hung in CLOSE_WAIT.
The second you quit Safari, all of these CLOSE_WAIT's immediately move to the LAST_ACK state, and then close on out normally.