[desktop-discuss] Re: at-spi-registryd

[Brian Nitz]

Ian Collins wrote:
> Padraig O'Briain wrote:
>
>   
>> The at-spi-registryd process should be started only when accessibiulity is enabled. There is (was?) a  bug in xscreensaver which caused at-spi-registryd process to be started when it should not have been.   
>>     
Yes this bug is still open:
6395649 at-spi-registryd starts when SunRay card is reinserted even when 
accessible device support is off

>> I don't think I've enabled it, I use the default settings for everything
>> except the background.  

>> As to the amount of RAM it is consuming could you post pmap output?
>>
>>  
>>     1093:   /usr/lib/at-spi-registryd
>> --oaf-activate-iid=OAFIID:Accessibility_Regi
>> 08041000      28K rwx--    [ stack ]
>> 08050000      36K r-x--  /usr/lib/at-spi-registryd
>> 08068000       8K rwx--  /usr/lib/at-spi-registryd
>> 0806A000  325080K rwx--    [ heap ] <---------------!!!!! Ian.
I was able to reproduce 6395649 on our test Sun Ray server and noticed 
that once at-spi-registryd is running, the heap grows, seemingly with 
every event:
Freshly started at-spi-registryd (pid=22526):
bash-3.00$ pmap -x 22526 | grep heap
0002C000     552     544     544       - rwx--    [ heap ]

Pull out and replace javacard:

bash-3.00$ pmap -x 22526 | grep heap
0002C000     568     560     560       - rwx--    [ heap ]

Pull out and replace javacard:

bash-3.00$ pmap -x 22526 | grep heap
0002C000     576     568     568       - rwx--    [ heap ]

Move the mouse around, launch some windows, click focus...
 pmap -x 22526 | grep heap
0002C000    1384    1376    1376       - rwx--    [ heap ]

I don't know if this slow growth of the heap could account for what you 
are seeing.  How long do you figure the at-spi-registryd process was 
running on your machine?