| View previous topic :: View next topic |
| Author |
Message |
linux-gamer
n00b
Joined: 30 Jan 2017
Posts: 12
|
 Posted: Wed Sep 20, 2017 7:28 pm Post subject: Code::Blocks, possible memory leak. [solved] |
 |
|
Hello everyone, this week I decided to install Code::Blocks to test, I really liked the IDE, but I found a annoying bug, whenever I open any file or a project, CPU usage goes to 100% (single core) and the use of RAM increases without stopping until I simply crash the whole computer because of SWAP, I've been investigating the code, but I'm kind of lost, because I'm not from C++, another observation, when I open the project and close the IDE, RAM usage continues to rise and CPU usage continues high, but the process does not terminate.
Edit 0: I forgot to speak... Disabling the plugin "compiler" everything is normal, so the problem is in it, I also tried to compile in the hand other than Portage, but it stays the same. I'll be testing the same version on Ubuntu 16.04, version 13.12 is functional, I'll try the latest version now.
Edit 1: As expected, in Ubuntu it was normal. 
Edit 2: If I disable the plugin, open the project and enable the plugin, everything stays normal... :/
Thank you very much in advance.
English is not my language, if I have something wrong, excuses. 
"Fix": Disable the Use Flag "pch".
Thank you all.
Last edited by linux-gamer on Sat Sep 30, 2017 7:22 pm; edited 2 times in total |
|
| Back to top |
|
 |
Yamakuzure
Advocate
Joined: 21 Jun 2006
Posts: 2285
Location: Adendorf, Germany
|
| Posted: Tue Sep 26, 2017 9:25 am Post subject: |
|
|
Which Version do you install? I am using dev-util/codeblocks-9999 (with USE="contrib -debug -pch -static-libs") for years now and never had a memory leak or anything like that.
When you open a project, it gets analysed, meaning all source files and their includes get parsed. That can take a while but rarely more than a few seconds.
See here: | Code: | PID USER PR NI VIRT RES %CPU %MEM TIME+ S COMMAND
31494 sed 20 0 1515.1m 150.8m 0.0 0.5 2:21.88 S codeblocks |
_________________
Important German:- "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
- "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
|
|
| Back to top |
|
|
C5ace
Guru
Joined: 23 Dec 2013
Posts: 474
Location: Brisbane, Australia
|
| Posted: Tue Sep 26, 2017 1:38 pm Post subject: |
|
|
Same problem here.
My fix is to start Codeblocks 16.01 from a Xfce-terminal.
Create a desktop icon:
| Code: | [Desktop Entry]
Version=1.0
Type=Application
Name=Code::Blocks IDE
Comment=Configurable and extensible IDE
Exec=codeblocks %F
Icon=codeblocks
Path=
Terminal=true
StartupNotify=true |
|
|
| Back to top |
|
|
linux-gamer
n00b
Joined: 30 Jan 2017
Posts: 12
|
| Posted: Thu Sep 28, 2017 9:05 pm Post subject: |
|
|
| Yamakuzure wrote: | Which Version do you install? I am using dev-util/codeblocks-9999 (with USE="contrib -debug -pch -static-libs") for years now and never had a memory leak or anything like that.
When you open a project, it gets analysed, meaning all source files and their includes get parsed. That can take a while but rarely more than a few seconds.
See here: | Code: | PID USER PR NI VIRT RES %CPU %MEM TIME+ S COMMAND
31494 sed 20 0 1515.1m 150.8m 0.0 0.5 2:21.88 S codeblocks |
|
Hi Yamakuzure, thank you for responding, checking the Use Flags I noticed that the "pch" was enabled, incredible as it may seem, it was the culprit because of this, now everything is normal.
Thank you for your time. |
|
| Back to top |
|
|
R0b0t1
Apprentice
Joined: 05 Jun 2008
Posts: 264
|
| Posted: Thu Sep 28, 2017 11:25 pm Post subject: |
|
|
I vaguely remember this being a known bug. The "fix" was as C5ace described. Can you check Gentoo's Bugzilla as well as the Code::Blocks Bugzilla?
Otherwise, I second the recommendation to use the **9999 ebuild or to track their repository yourself. If you are going to follow development, a project's live code is usually more bug free than the very new releases (depending on the maturity of the project, etc). |
|
| Back to top |
|
|
linux-gamer
n00b
Joined: 30 Jan 2017
Posts: 12
|
| Posted: Sat Sep 30, 2017 7:08 pm Post subject: |
|
|
| R0b0t1 wrote: | I vaguely remember this being a known bug. The "fix" was as C5ace described. Can you check Gentoo's Bugzilla as well as the Code::Blocks Bugzilla?
Otherwise, I second the recommendation to use the **9999 ebuild or to track their repository yourself. If you are going to follow development, a project's live code is usually more bug free than the very new releases (depending on the maturity of the project, etc). |
Hello, thanks for replying, I had already tested the alternative of colleague C5ace, but it had not worked for me, in a few minutes it consumed all the RAM, closing only in a kill -9 or in CTRL + C. Before turning to this forum, I had already visited both others looking for bugs related to this, but had not found, the problem occurred while using the Use Flag "pch", disabling it, everything returned to normal. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
