thank for the explanation thomas.
It seems like this is a matter of some complexity. I am not sure how to continue from here as it seems like there is no easy way. But I think i will be looking a little into the code myself, for my own understandig of the problems.
I guess you experts knows the code like your own pocket, so I have much learning to do:-)
I did some thread investigation by the use of ProcessExplorer from former sysinternal:
And the main thread call stack typically looks like this:
ntkrnlpa.exe!ZwYieldExecution+0x1c80
ntdll.dll!KiFastSystemCallRet
kernel32.dll!FindFirstFileW+0x16
kernel32.dll!GetLongPathNameW+0x1d2
wxmsw28u_gcc_cb.dll!ZNK10wxFileName11GetLongPathEv+0x57
wxmsw28u_gcc_cb.dll!ZN10wxFileName9NormalizeEiRK8wxString12wxPathFormat+0x3c3
wxmsw28u_gcc_cb.dll!ZN10wxFileName14MakeRelativeToERK8wxString12wxPathFormat+0x51
codeblocks.dll!ZN9cbProject9BuildTreeEP10wxTreeCtrlRK12wxTreeItemIdbbP19FilesGroupsAndMasks+0x689
codeblocks.dll!ZN14ProjectManager17EndLoadingProjectEP9cbProject+0xdc
codeblocks.dll!ZN14ProjectManager11LoadProjectERK8wxStringb+0x173
codeblocks.exe+0x2f5eb
codeblocks.exe+0x2f990
codeblocks.exe+0x31206
codeblocks.exe+0x1b3c
codeblocks.exe+0x6e8a
codeblocks.exe!ZN12cbToolPlugin9BuildMenuEP9wxMenuBar+0xa8
wxmsw28u_gcc_cb.dll!Z12wxInitializeiPPw+0x9a
wxmsw28u_gcc_cb.dll!Z7wxEntryP11HINSTANCE__S0_Pci+0xd8
codeblocks.exe+0x724e
codeblocks.exe+0x56718
codeblocks.exe+0x124b
codeblocks.exe+0x12b8
kernel32.dll!RegisterWaitForInputIdle+0x49
At least it seems that the code completion plugin is not much in fokus at project load time.