|
|
Speaking of memory leaks -- lookupd?
Has anyone else noticed lookupd consuming (and not releasing) large amounts of memory? I've sometimes noticed lookupd consuming hundreds of megs of RPRVT memory after doing lots of name resolutions (I run a news aggregator, sendmail, and Apache, all of which are doing lots of DNS lookups.) After a couple of days, I've sometimes seen lookupd with a half gig of memory allocated. Restarting lookupd (via "sudo /System/Library/SystemConfiguration/Kicker.bundle/Resources/restart-lookupd") frees up several hundred megs of VM.
Speaking of memory leaks -- lookupd?
Noticed your post since I'm currently trying to debug a excessive memory usage problem with lookupd on my 10.2.6 iBook 600. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|