[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 229602] Parsing freeze UI when reading program's output directory
From:       Nicolas Bigaouette <nbigaouette () gmail ! com>
Date:       2011-11-30 16:29:33
Message-ID: E1RVn2L-0001yH-UN () bugs ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=229602





--- Comment #21 from Nicolas Bigaouette <nbigaouette gmail com>  2011-11-30 16:29:33 ---
Thanks Milian for your suggestions. I am indeed using a custom make file. I
will try to build KDevelop from git and report back.

I added .kdev_ignore files to each output* folder I had (15 of them). Loading
the project now half-works. The GUI is responsive, I can continue editing, but
the background parser is stucked at 0%, with 100% cpu (on one core) and 28% or
RAM (~5GB). Is KDevelop going into subfolders, even if a .kdev_ignore is
present in the parent folder?

I tried cloning my git repo (so there wouldn't be any data folders) and
creating a big file using dd (dd if=/dev/zero and dd if=/dev/null). I went up
to 500GB for the empty/sparse file (from /dev/null) and 50GB with zeros but it
went fine: kdevelop went over it quite fast.

What I could do is build a reduced version of my code that just outputs a lot
of data. If I remember correctly, the behavior is worst when many many small
files are created. Bigger files outputed less often does not show the problem.

I understand though that running an untrusted binary is not something we want
to do. I'll create a repo instead with a basic project that can, hopefully,
identify the problem.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]