Menu

#479 Abnormal 100% CPU using

Undefined
open
nobody
None
Bug_Report
2017-02-17
2017-02-16
No

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

Discussion

  • Teodor Petrov

    Teodor Petrov - 2017-02-16

    Can you use gdb or perf to find out where the cpu cycles are wasted?

     
  • George Galeev

    George Galeev - 2017-02-16

    perf report (main parts)

    # Children   Self   Command          Shared Object
    
        64.95%    64.82%  codeblocks       libgamin-1.so.0.1.10
                     |          
                     |--49.30%-- 0
                     |          |          
                     |          |--27.32%-- FAMPending
                     |          |          
                     |           --21.98%-- FAMNextEvent
                     |          
                     |--0.08%-- FAMPending
    
    ...
        49.43%     0.00%  codeblocks       [unknown]
                     |
                     ---0
                        |
                        |--22.03%-- FAMNextEvent
    ...
                        |--27.40%-- FAMPending
    ...
                        |          
                         --0.00%-- DirMonitorThread::Entry
                                   apic_timer_interrupt
    
       18.29%    18.28%  codeblocks       libFileManager.so
                     |
                      ---DirMonitorThread::Entry
                                 apic_timer_interrupt
    
     
  • Teodor Petrov

    Teodor Petrov - 2017-02-17

    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 :)

     
  • George Galeev

    George Galeev - 2017-02-17

    Ok, I don't know for what this plugin, I have it with standard installation. I turned it off and everything was fine.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.