KDevelop using 100% of CPU all the time

Benjamin CAILLAT bcaillat at gmail.com
Thu Jul 20 22:04:32 BST 2017

A simple ext4:
/dev/dm-2      ext4

The only particularity is I use LVM + full disk encryption, but I doubt
that could be an issue. I actually have no idea why KDevelop uses FUSE.

My project directory contains ~2600 dir, but most of them are in .git/
(ignored by the project). The rest represents ~150 directories, which does
not seem a lot to me.

Thanks again for the follow up, let me know if you have any idea why FUSE
is used!


On Thu, Jul 20, 2017 at 2:36 PM, René J.V. Bertin <rjvbertin at gmail.com>

> On Thursday July 20 2017 09:18:35 Benjamin CAILLAT wrote:
> >Thank you for your answer! It seems to be related to FUSE:
> >
> >(gdb) bt
> >#0  sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:85
> >#1  0x00007f2d83b57018 in fuse_session_loop_mt () from
> /lib/x86_64-linux-gnu/libfuse.so.2
> >#2  0x00007f2d83b5bfc7 in fuse_loop_mt () from
> /lib/x86_64-linux-gnu/libfuse.so.2
> >#3  0x00007f2d83b5e985 in ?? () from /lib/x86_64-linux-gnu/libfuse.so.2
> >#4  0x00000000004024c1 in main ()
> On what kind of filesystem is your project hosted? KDevelop sets up
> directory watchers for all directories in your project, and I wouldn't be
> very surprised if for FUSE-based filesystems that means running a polling
> loop. It does seem incongruous though that this would eat 100% CPU; I don't
> think KDevelop needs to know about changes in the project source tree with
> millisecond precision...
> R.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop/attachments/20170720/09288ad8/attachment.html>

More information about the KDevelop mailing list