Re: gconfd process eating CPU

Hi,

On Fri, 2004-12-17 at 17:31 -0600, Brian Cameron wrote:

> Such sick gconfd-2 processes have the following stack trace:
> 
>    core 'core.64457' of 64457:     /usr/lib/gconfd-2 13
>     ff19d9c8 _poll    (39660, d, 7055, 56240, 0, 3) + 8
>     ff22a28c g_main_context_poll (35e20, 7055, 7fffffff, 39660, d, ff280410) + d4
>     ff2294cc g_main_context_iterate (35e20, 1, 1, 0, 35e28, 39660) + 37c
>     ff229e00 g_main_loop_run (3dfd8, 1, 0, ff282c54, 2c3f0, 400) + 300
>     000167c4 gconf_main (3dfd8, 17400, 2a000, 2ad58, 0, 2ac2c) + 90
>     00016508 main     (0, fbc9, 2abd4, 0, 18fe8, 33b88) + 4d8
>     000130d0 _start   (0, 0, 0, 0, 0, 0) + 108
> 
> Unfortunately, that doesn't really give me much of a hint of what is going
> wrong with gconfd-2. 

	One possibility is that one of the file descriptors we are polling has
a pending condition which we aren't processing or that the file
descriptor was closed but never removed from the poll. An strace of
gconfd-2 would help you figure out if that is the case.

Cheers,
Mark.