https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #4 from RJVB <rjvber...@gmail.com> --- There's something else that's fishy, I'm now pretty certain that the CPU burning is due to an issue in the AbstractFileManagerPlugin and/or the FileManagerListJob classes which somehow start reloading all or part of a project continuously. Hard to tell exactly what happens but I didn't see any trace of my ProjectWatcher class causing this directly (activating a trace in AFMPP::dirty() doesn't print anything). The project that's causing this is one using autoconf, and the issue started when I made an edit to its configure.ac . Looks like this starts an infinite loop; autoconf is apparently called automatically and since the edit is incomplete there's an error situation somewhere which isn't handled properly. This doesn't always cause signals to be delivered to a stale ProjectWatcher class but it seems I do have to rethink my design a bit :-/ -- You are receiving this mail because: You are watching all bug changes.
