User forums > Help
Code::Blocks is really slow. How do I fix it?
ollydbg:
--- Quote from: Pecan on August 22, 2013, 05:18:44 pm ---Change the setting to "Current Project's symbols" and see if the problem goes away.
ImageCraft found a quirk in CalculateCommonTopLevelPath() which sets the top level path to the root of the hard drive. This causes CodeCompletion to start all searches from the root of the hard drive. You might have hit this problem.
--- End quote ---
What does "ImageCraft" means? Does it mean this IDE https://www.imagecraft.com/ ? It looks its a C::B fork?
EDIT:
In the page: https://www.imagecraft.com/devtools_AVR.html
I see such statement:
--- Quote ---The V8 products use CodeBlocks as the IDE. Per GPL requirements, you may download the modified source code (trunk SVN8162) here. http://imagecraft.com/pub/ICC_CB_SVN8162.7z
--- End quote ---
Wyrm:
I had another one of those slowdowns. Switching symbol settings didn't help, and my symbol list was only about 20.
In fact, not just the editor, everything became slowish. Switching to another tab - half a second delay. Moving separator - half a second delay. Switching from projects to symbols - a second delay.
In addition, I started having visual artifacts, a rectangle from another part of the code kept hanging around. To get to this point I kept C::B open for about 2 days without a restart.
Top showed that Xorg CPU usage shot up to 80% and Kwin started showing up high on top as well. Xorg lingers at the top of the CPU usage (in the range of 50% - 80%) for about 10 seconds if I don't touch C::B and then gradually goes down to single digits. Whenever I try to do anything in C::B Xorg CPU usage would go up again.
I have a 7MB video of this slowdown. Unfortunately, the mouse pointer is not recorded, so it is hard to judge the delay from the video.
Edit: my system and C::B version are listed in the previous post.
ollydbg:
@Wyrm
Is it possible to post your testing project and the steps here?
Because without this, other one can not reproduce this bug. Thanks.
BTW: I can help to test on Windows system.
Wyrm:
--- Quote from: ollydbg on August 23, 2013, 09:11:02 am ---@Wyrm
Is it possible to post your testing project and the steps here?
Because without this, other one can not reproduce this bug. Thanks.
BTW: I can help to test on Windows system.
--- End quote ---
Thanks for the offer. Let me first try to troubleshoot it on my side. Besides, I'm not sure if it is reproducible on a Microsoft platform. If it is an X-windows resource leaking then it's unlikely that you'll see it.
The steps I want to take are these:
* I need to upgrade my C::B anyways. It's compiled with Dec 9, 2012 source code. The newer version may not exhibit this problem.
* When I compile the new source I'll add "-g" to the release build to include debug symbols.
* If the new version gets slow I'll attach one of my debuggers to it and get a handful of stack traces. I also have access to some commercial debuggers and profilers which may help to investigate this.
So far I've been delaying this exercise because a simple restart fixes all problems. We all work with tight schedules and it's hard to justify major time investment when 3 seconds is all it takes to work around the issue. I will try to get to it in the next couple of weeks.
Navigation
[0] Message Index
[*] Previous page
Go to full version