Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Speaking of memory leaks -- lookupd?' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Speaking of memory leaks -- lookupd?
Authored by: marmoset on Nov 11, '02 07:51:17AM

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.



[ Reply to This | # ]
Speaking of memory leaks -- lookupd?
Authored by: sjk on Sep 19, '03 05:09:35PM

Noticed your post since I'm currently trying to debug a excessive memory usage problem with lookupd on my 10.2.6 iBook 600.

If I run fs_usage on the process it spits out lines like this (among others) every second or two:

11:04:08 stat private/etc/hosts 0.000095 lookupd
11:04:08 open private/etc/hosts 0.000034 lookupd

I have a generic configuration (e.g. no changes to LookupOrder). I don't know what's normal for this because this is my only Mac OS X system but I'm sure it shouldn't be consuming as much memory as it does over a relatively short time. My search for answers continues...



[ Reply to This | # ]