Re: [gamin] Re: [BUG?] Gamin locks up the machine in KDE



Le dimanche 06 février 2005 à 13:57 +0100, Frederik Himpe a écrit :
> On Mon, 10 Jan 2005 15:10:51 +0100, Francesco Biscani wrote:
> 
> > On Monday 10 January 2005 14:51, Daniel Veillard wrote:
> >> On Mon, Jan 10, 2005 at 12:17:19PM +0100, Francesco Biscani wrote:
> >> > I'm using gamin with inotify on KDE and I must say that it is very good.
> >> > I have only one complaint with it, i.e. it locks the machine under
> >> > determined circumstances. It happens when I try to unmount a device when
> >> > Konqueror is opened on the mountpoint of that device. The machine simply
> >> > locks up. I think it goes into a loop because after some seconds the fan
> >> > of the laptop turns on, as if there were a lot of CPU activity going on.
> >>
> >>   Sounds like a loop in the inotify code in the kernel.
> 
> There seems to be the same/a related problem in Mandrakelinux 10.2
> beta/Cooker, see http://qa.mandrakesoft.com/show_bug.cgi?id=13424 .
> The problem is that the kded process gets stuck in an endless loop when
> update-menus to update the Debian menu system, is run.
> 
> We are starting to suspect this is caused by gamin, and not by inotify,
> because someone reports to have it with both an inotify enabled kernel,
> and a kernel without inotify support. Replacing gamin by fam, seems to
> stop the problem.

I doubt it is caused by gamin or inotify.

I guess kde is simply re-reading files again and again when they are
re-created by update-menus instead of just reading them one time when
needed (ie when menu is opened or after a timeout) to prevent this.

I had the same problem with fam and gamin in initial XDG implementation
for gnome-panel but with Mark McLoughlin, we figured a way to fix it
properly.

-- 
Frederic Crozat <fcrozat mandrakesoft com>
Mandrakesoft




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]