Re: KDevelop using 100% of CPU all the time
René J.V. Bertin <[email protected]>
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <23850638.nXr6fIz1HY@bola> |
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.