Re: Leaky at-spi-registryd update

["Nolan Darilek" <nolan thewordnerd info>]

OK, I take back everything I said. On my netbook now, at-spi-registryd 
has 33% of its 1G of RAM. Performance isn't as bad since I'm not using 
swap on an SSD, but it isn't the hardware on that box, nor is it 
something I custom installed and forgot about.

The only commonality I can think of is that both these boxes are running 
very close to their memory capacity. Maybe that's what should be used to 
debug this. Load an up-to-date intrepid system nearly to capacity, run 
Orca trunk and use FF/Thunderbird for a while...


On 02/18/2009 11:07 AM, Willie Walker wrote:
> > The power supply in that box died last night. Since I'm going to have 
> > to open it anyway, I'll upgrade its 512 megs of RAM to a gig and see 
> > if that helps. And since no one else on multiple lists seems to have 
> > seen this behavior, I'm going to call it bad hardware until proven 
> > otherwise.
>
> Heh - I'd love to call it a "bad bit" and be done with it.  :-)  But, 
> you might also have some unique usage pattern that's exposing a 
> serious flaw in the infrastructure.  Maybe something's bumping into 
> the RAM barrier and causing things to go swap-bound, but I'm not sure 
> why that would cause the registry to go nuts.
>
> Keep us posted on what you find with the new hardware.
>
> Will