User forums > Using Code::Blocks
Bug Report: [#18755] C::B hangs for 20 seconds while opening large project...
dmoore:
btw, it takes about 8s to open the C::B cbp on a pretty beefy Win 7, 64 bit system with no open editors. (CC on/off makes no difference.) Is that normal?
rickg22:
--- Quote from: jens on October 16, 2012, 10:26:23 pm ---Did you compare the default.conf's from at work and the system with the lag ?
--- End quote ---
Not yet, I'm still at work.
--- Quote ---Do you have any network shares, that might be involved ?
--- End quote ---
Not that I know of.
--- Quote ---Did you try it with the exact same copy of C::B at both systems (packed here and unpacked there in a clean folder) ?
--- End quote ---
The one at work seems to have another wxWidgets.dll, and I think I copied it to the system folder (at work). The C::B folder was zipped and unzipped pristine from c:\cb at work, to c:\cb at home. I had to download the wxWidgets dll separately (at home I used the one you provided), so that might be a candidate.
--- Quote ---Are the related paths the same ?
--- End quote ---
At home I'm using a WAMP, at work I'm using a XAMPP. Both have a long url before the www, and both are shortcutted with a symlink (using Window's mklink command) to c:\htdocs. Note that there's no difference between opening the original path and the symlinked one, both take the same to open.
[/quote]
--- Quote ---Are there any probaly related (outdated) libs in the search path ?
--- End quote ---
Okay, I did not check that one. Are you saying home's C::B is using another lib? Is there a way to find out which libraries (dlls I suppose) C::B is using at runtime? (Is there a plugin for that, for example?)
Jenna:
--- Quote from: rickg22 on October 16, 2012, 11:41:06 pm ---
--- Quote ---Are there any probaly related (outdated) libs in the search path ?
--- End quote ---
Okay, I did not check that one. Are you saying home's C::B is using another lib? Is there a way to find out which libraries (dlls I suppose) C::B is using at runtime? (Is there a plugin for that, for example?)
--- End quote ---
You can run C::B through dependency walker: http://www.dependencywalker.com/ .
rickg22:
OK, before anything, thank you so much for your support guys. Your suggestions and interest are really a relief.
So, I'm compiling wxWidgets right now to compile C::B from source. I'll keep you posted.
BTW, opening the C::B project itself only took around 5 seconds delay.
dmoore:
--- Quote from: rickg22 on October 17, 2012, 04:41:55 am ---OK, before anything, thank you so much for your support guys. Your suggestions and interest are really a relief.
So, I'm compiling wxWidgets right now to compile C::B from source. I'll keep you posted.
BTW, opening the C::B project itself only took around 5 seconds delay.
--- End quote ---
I did a little profiling of the time it takes to load the C::B project on my Win7 PC. It looked like most of the time was taken on the rebuilding the project manager tree view. Loading the project file and creating the project instance was very fast. Loading the C::B unix project (including building the tree view) takes less than a second on my lesser spec'd Ubuntu machine at home (actually it looks almost instantaneous after the first time).
EDIT: This could be relevant http://forums.wxwidgets.org/viewtopic.php?f=1&t=35118 but we only open a few nodes at most... Maybe this too http://forums.wxwidgets.org/viewtopic.php?t=16124&p=71104
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version