Re: Leaking at-spi-registryd

[Nolan Darilek <nolan thewordnerd info>]

OK, think I picked the wrong failing technology. Before, I noticed a
spike in activity when at-spi-registryd started using more resources,
which it didn't for some time of use, so I assumed it was at fault. On a
whim, I stopped using Shredder and after several hours of heavy use,
at-spi-registryd is at about 18% memory usage and my system is almost as
snappy as it was when I started. So I'm not entirely sure why it happily
only uses 0.7% or so for a while then suddenly spikes up to 18, but
Thunderbird seems far more responsible than at-spi-registryd.

Sorry for the false alarm.


On Tue, 2009-01-13 at 11:48 +0800, Li Yuan wrote:
> Hi Nolan,
> 
> I didn't notice serious leak in at-spi-registryd. I will take a look at 
> it these days.
> 
> Nolan Darilek wrote:
> >
> >
> > I tried checking out the latest at-spi-registryd from subversion. I 
> > use stow to keep all locally-installed stuff separate and removable 
> > from distribution-installed packages. I have 
> > /usr/local/libexec/at-spi/at-spi-registryd, but 
> > /usr/lib/at-spi/at-spi-registryd is still being started. How can I 
> > start my own locally installed at-spi-registryd without replacing the 
> > Ubuntu packaged version?
> You need to build gnome-session to start the right at-spi-registryd. But 
> this is harder than just replace the system at-spi-registryd.
> >
> > Until I figure this out, is there some way of stopping/restarting 
> > at-spi-registryd mid-session? I tried killing it, but after that point 
> > I was unable to get to a prompt where I could start a new instance. 
> > Generally I can tell that I'm at a terminal or in the run dialog 
> > because backspace on an empty line emits a beep, but nothing I did 
> > brought me to this point.
> After you kill at-spi-registryd, the GUI event can not be passed to ATs, 
> so it shouldn't be killed mid-session.
> 
> Regards,
> Li