User forums > Using Code::Blocks

Bug Report: [#18755] C::B hangs for 20 seconds while opening large project...

(1/20) > >>

rickg22:
I found this bug this week. At first I thought it had to do with directory traversal (old bug), but it seems it's not the case.

https://developer.berlios.de/bugs/?func=detailbug&bug_id=18755&group_id=5358


--- Quote ---Original Submission:
I have a PHP project under a WAMP directory (with a symlink on c:\htdocs for easy access) under Windows 7 32 bit.

Build info:

Build: Oct 13, 2012 18:50:41 - wx 2.8.12 (Windows, unicode) - 32 bit
"Version: svn build rev 8455
SDK Version: 1.13.11"

I noticed that when I open this particular project, Code::Blocks takes 22 seconds to open the project. Even when I add a file, it's painfully slow.

While this project is loaded, loading even trivial projects (like a hello world located elsewhere) takes 17 seconds.

It happened with the 8248 nightly, but also with the October 7 nightly 8438 and with 8455 (latest available at the time of this report). I can't replicate the bug at work, so it might be a rare case. I'll attach some files to add more info.

--- End quote ---

It's a long PHP project, with 2121 files including several javascript toolkits in it (ExtJS, jQuery, etc). Notice that I set up a different directory for the "executable" under build options to not disturb the source tree (maybe that's it, but I can't be sure, I'm attaching the cbp file just in case).

The last thing I saw was
"Project data set for C:\htdocs\SIG\SGPG\js\app\common\commonfuncs.js
Top Editor: C:\htdocs\SIG\SGPG\js\app\common\commonfuncs.js "

After this, I get the 20 sec hang, and finally, the environment variables are loaded.
A way to solve this would be to add more debug messages on each stage of project loading (or whatever post-loading stuff is done).

After loaded, adding a file takes 7 seconds (I'm in the middle of refactoring an urgent project, this is a royal pain in the arse guys and my job might be at stake :( Please help! )

I can share the full project to individual developers on request, if needed.

(EDIT: Unattached project file for confidentiality)

rickg22:
I can't attach the full project in public, it's confidential stuff (doh) and over 64 megs...

the easiest thing would be to add debugging breadcrumbs to print messages on the debug window to see where the hang happens... (I might need to be given a patched build for this so I can test)

Well, I'm off to work. Keep me updated.

rickg22:
Attaching my default.conf file... (this one's at home)

MortenMacFly:
...In wonder if you can pin-point the hang to a particular file. What happens, if you remove all but the ones mentioned in the log?

- Also, are there any non *.js files? What, if you remove files of certain type(s) step-by-step?
- Also, does it change if you remove the *.layout file?
- Also, is it generally related to the number of files? I.e. if you remove "half" of the files, is it loaded twice as fast?

BTW: I just opened the project file - works fine and fast here... I'm afraid this is of no help.

oBFusCATed:
Why don't you build a debug build of C::B and use the debugger to break it when it is hanged?
I'm sure you'll pinpoint the slow function/code.

Navigation

[0] Message Index

[#] Next page