Codeblocks process using 100% CPU load right after launch. And still running (with 100% load) after the application closed (in any way, ctrl + q, or close window button). At full load will be so much cpu cores as much runned codeblocks applications (including closed, after work need to kill). App itself is functioning normally (open projects, compile, etc).
If the application is run from the console (command from console), the behavior is ordinary: CPU load standard, process disappears from the list of running after normal closing.
I observe this behavior last about two-three years in the nightly builds and now in the 16.01 release.
Code::Blocks Release 16.01 rev 10692 - wx2.8.12 (Linux, unicode) - 64 bit
Linux 4.9.6-gentoo-r1 x86_64, KDE 4 and 5
Can you use gdb or perf to find out where the cpu cycles are wasted?
perf report (main parts)
Disable the file manager plugin and all will be back to close to 0% cpu usage. If you use the file manager plugin, then you'll have to debug it and then provide patches :)
Ok, I don't know for what this plugin, I have it with standard installation. I turned it off and everything was fine.