User forums > Using Code::Blocks

cb hangs and I get "Pool task operated?!" message

<< < (4/5) > >>

oBFusCATed:

--- Quote from: erezz on October 30, 2013, 09:10:48 am ---which is a total of 1705 files. It sounds strange to me that going over 1705 files takes ~30 seconds, even if it's on a network fs.

--- End quote ---
Probably you can strace codeblocks to see what going on and where it is slow.

Jenna:
The network I/O is very slow even on fast networks, especially on windows shares (my experience from windows to windows and even worse from linux to windows).

For the statistics, we have fantastic plugin in contrib-plugins. Just open "Plugins -> Code statistics".

Jenna:
By the way: one real evil thing is that C::B always looks for changed files, if it regains focus.
That can be really slow on network shares if you have multiple files open.

If I find the time, I will add a (per project) option, that can switch this off.

erezz:
I ran c::b with strace and I saw that stat64() gets called for files that are not included in my project. My project is located in ~/dir1/dir2/myproj. I see that stat64() gets called for files in ~/dir1/dir2/otherproj. Unfortunately, otherproj is huge, so it may take time to go over all its files.

Am I doing something wrong? Is it something in my project configuration?

Thanks,
Erez

erezz:

--- Quote from: erezz on October 30, 2013, 02:48:12 pm ---I ran c::b with strace and I saw that stat64() gets called for files that are not included in my project. My project is located in ~/dir1/dir2/myproj. I see that stat64() gets called for files in ~/dir1/dir2/otherproj. Unfortunately, otherproj is huge, so it may take time to go over all its files.

Am I doing something wrong? Is it something in my project configuration?

Thanks,
Erez

--- End quote ---

One more thing - the c::b project (i.e. bmarks, cbp & layout files) is located at ~/dir1/dir2/codeblocks_proj/proj_name.

Erez

Navigation

[0] Message Index

[#] Next page

[*] Previous page