Bug#576617: libgconf2-4: gconfd-2 enters infinite loop, preventing other apps from starting forever

Josselin Mouette joss at debian.org
Wed Apr 7 09:33:58 UTC 2010


Le mardi 06 avril 2010 à 21:31 +0200, Helge Hafting a écrit :
> > Does it only happen with Mozilla programs, or with all programs using
> > GConf? Try for example gcalctool.
> > 
> "gcalctool" is just as bad as icedove.
> gconfd-2 and gcalctool both eats 100% cpu forever.
> I get a blank unresponsive gcalctool window.
> 
> strace gcalctool
> reveals that this sequence repeats over and over:
> read(15, 0x25d5104, 4096)               = -1 EAGAIN (Resource temporarily unavailable)
> poll([{fd=6, events=POLLIN}, {fd=8, events=POLLIN|POLLPRI}, {fd=11, events=POLLIN|POLLPRI}, {fd=12, events=POLLIN|POLLPRI}, {fd=13, events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI}, {fd=15, events=POLLIN}, {fd=16, events=POLLIN}], 8, 0) = 1 ([{fd=12, revents=POLLHUP}])

What is file descriptor #15 ? (You can look at which open or pipe system
call returns 15 earlier in the strace.)

It would also be interesting to obtain a GDB backtrace of what is
happening at that moment. See http://wiki.debian.org/HowToGetABacktrace

> dbus-launch iceweasel
> gives me a blank iceweasel window, and two processes
> (firefox-bin and gconfd-2) eating 100% cpu each.

OK so it’s probably not D-Bus related.

Cheers,
-- 
 .''`.      Josselin Mouette
: :' :
`. `'   “A handshake with whitnesses is the same
  `-     as a signed contact.”  -- Jörg Schilling







More information about the pkg-gnome-maintainers mailing list