On 2007-12-13, Martijn Dekker <martijn@inlv.demon.nl> wrote:
> In article <martijn-3394C1.12533711122007@news.individual.net>,
> Martijn Dekker <martijn@inlv.demon.nl> wrote:
>
>> In article <Jjo7j.14245$Mu4.13532@bignews7.bellsouth.net>,
>> Robby Workman <newsgroups@rlworkman.net> wrote:
> [...]
>> > That being said, there were a lot of fixes in the hal release
>> > that's now in -current, so you might try building that version
>> > on your 12.0 box (be sure to build hal-info too - 0.5.10 requires
>> > the newer hal-info vice versa) [1]
>>
>> Thanks, I've tried that. So far, so good -- in a few days to a week I'll
>> know whether it helped.
>
> Nope, didn't help. After two days, hald from HAL 0.5.10 is already up to
> 8.6% of total memory space. It started out at 2.0%.
>
> I'm stumped. AFAIK, I'm using the default configuration -- I didn't
> change anything. Does anyone have any idea where to start looking?


Well, crap.

I've never used valgrind, so I honestly have no idea how to go about
employing it, but supposedly this idea is its purpose:
http://slackbuilds.org/repository/12...ment/valgrind/

This is probably worth a mail to the hal mailing list:
http://lists.freedesktop.org/mailman/listinfo/hal
to see if the devs know of any existing leaks and get some other
troubleshooting ideas.

-RW