FS#39473 - [codeblocks] progressively occupying the RAM

Attached to Project: Community Packages
Opened by ian (ianclever) - Sunday, 16 March 2014, 01:38 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Monday, 24 March 2014, 15:26 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

code blocks 13.12-2 package that is part of this comunity repository progressively occupying the RAM (in my case almost managed to catch, a missed 100MB to occupy everything, it was just time to kill), if programmed in c bet at some malloc error, but is not as opinarei not, the error occurred when opening a single file *. c of less than 100 lines, the occupation of memory occurs in jumps of about 2MB each second, and it continues even if you close it the normal way (by clicking the x button), just to fill the RAM after killing manually, use lxde graphical environment, and recently uploaded a lib ...-Wyland, is the information I have. awaiting.
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Monday, 24 March 2014, 15:26 GMT
Reason for closing:  None
Additional comments about closing:  See comments.
Comment by Bartłomiej Piotrowski (Barthalion) - Sunday, 16 March 2014, 07:12 GMT
It doesn't seem to be a packaging bug. Have you reported your issue upstream?
Comment by ian (ianclever) - Sunday, 16 March 2014, 12:14 GMT
not even going to do that now.
Comment by ian (ianclever) - Sunday, 16 March 2014, 15:38 GMT
I just report the error to the staff of codeblocks, follow the link:

http://developer.berlios.de/bugs/?func=detailbug&bug_id=19330&group_id=5358
Comment by ian (ianclever) - Monday, 24 March 2014, 09:52 GMT
  • Field changed: Percent Complete (100% → 0%)
discovered the possible cause of the problem
Comment by ian (ianclever) - Monday, 24 March 2014, 15:18 GMT
This week I made a crap who deleted my user, I had to create a new user for my arch, from this moment the codeblocks gave no problem, and there has been no recent update it, the last update was when it was the transition from arch 2013 to arch 2014. How the rolling distro is just upgraded. So I suppose the update version of the distro, for some reason she did not remove all the old files from codeblocks, and additionally wrote others in the same folder, and this might be what was causing a conflict and then occupying the RAM, I'm not sure, but I pray that test.

if the translation is bad, I'm sorry, I do not speak English and I'm using google translator.
Comment by Bartłomiej Piotrowski (Barthalion) - Monday, 24 March 2014, 15:26 GMT
Ok, so it's not easily reproducible problem and there is little value in looking for possible cause of it. Closing, I guess that no many users are affected.

Loading...