Author Topic: It seems CB will hang about 10+ seconds to load the codeblocks.cbp project  (Read 8561 times)

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5247
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Windows XP, SVN 6048 self build version(TDM GCC 4.4.1-2).
Does someone encounter the same problem?
Thanks
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Does someone encounter the same problem?
Not here.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline vix

  • Multiple posting newcomer
  • *
  • Posts: 60
Quote
Does someone encounter the same problem?
I have the same problem. The old svn 5911 works well.
I noticed that during this seconds the C::B CPU load is very high (more than 50%).

If you open C::B the program hangs for 5-6 seconds with high CPU load before you can start working. SVN 5911 works well.

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
Yes, I have such a feeling. And my side of the CB users, are also reflected in very slow start-CB!

Offline Loaden

  • Lives here!
  • ****
  • Posts: 1014
I think that the CB at boot time to load too many wizard, which in fact is unnecessary!
Now, CB boot speed is not much faster than the Eclipse CDT!
Even slower than the VS!

Offline blueshake

  • Regular
  • ***
  • Posts: 459
too many plugin.
Keep low and hear the sadness of little dog.
I fall in love with a girl,but I don't dare to tell her.What should I do?

Offline jens

  • Administrator
  • Lives here!
  • *****
  • Posts: 7265
    • Jens' unofficial debian-repository for the Code::Blocks - IDE
Does this happen just after starting blank C::B  ?

Please start it with -d form commandline to get the debug-output.
You might have to start C::B, go to the Code::Blocks debug panel in the logger-pane, close C::B and open it again, to make sur that you can see the debug log while starting.

I hope it works, because on my XP, the content of the log is not visible without scrolling it a tleast one time.

To make sure it's a plugin, you can disable them all and reenable them one after the other, or disable them one after the other, to see whether one of the plugins slows down C::B.

By the way I have no such issue on my XP box.

Offline vix

  • Multiple posting newcomer
  • *
  • Posts: 60
I don't think it's a problem of too many plugins because I have only the default ones (no additional ones).

Quote
Please start it with -d form commandline to get the debug-output.
You might have to start C::B, go to the Code::Blocks debug panel in the logger-pane, close C::B and open it again, to make sur that you can see the debug log while starting.
I verified that when C:B hangs, the last line of the debug panel is
Code: [Select]
Caching internal gcc dirs for adding to parser...
After some seconds the following lines appear
Code: [Select]
Caching GCC dir: c:\programmi\MinGW\lib\gcc\mingw32\4.4.1\include\c++
Caching GCC dir: c:\programmi\MinGW\lib\gcc\mingw32\4.4.1\include\c++\mingw32
Caching GCC dir: c:\programmi\MinGW\lib\gcc\mingw32\4.4.1\include\c++\backward
Caching GCC dir: c:\programmi\MinGW\include
Caching GCC dir: c:\programmi\MinGW\lib\gcc\mingw32\4.4.1\include
Caching GCC dir: c:\programmi\MinGW\lib\gcc\mingw32\4.4.1\include-fixed
and C::B is ready to operate

Quote
To make sure it's a plugin, you can disable them all and reenable them one after the other...
I tried, and the problem is in the "Code Completion" plugin.
If I enable only this one the problem happens. If I enable all the others, the problem doesn't happen.

I don't know if this helps, but I have C::B on C: drive, and the *.cbp, and workspaces on a different logical drive (D:\), that is a different logical partition on the same physical drive as C: