https://bugs.kde.org/show_bug.cgi?id=373017
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=373017
--- Comment #9 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular b
https://bugs.kde.org/show_bug.cgi?id=373017
Justin Zobel changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=373017
--- Comment #7 from Milian Wolff ---
@Sven, your idea can still fail. When we schedule, the clang parse jobs may not
yet use a lot of memory. But later when they hit $insane-template-magic-code
they suddenly sky-rocket memory wise and then we fail.
@JD
https://bugs.kde.org/show_bug.cgi?id=373017
--- Comment #6 from Sven Brauch ---
After a bit of quick looking around, I think one realistic option would be to
read current memory usage from /proc/1234/mem before starting a parse job, and
defer starting the job if that is already above a certain th
https://bugs.kde.org/show_bug.cgi?id=373017
--- Comment #5 from JDF ---
Here below are some links that might be useful. It seems that prlimit and
timeout can be interesting.
If you know that you have let's say 16GB on the machine, and the user wants
that 8GB maximum will be used for parsing and t
https://bugs.kde.org/show_bug.cgi?id=373017
--- Comment #4 from Milian Wolff ---
Yes, I agree. The question is: how? ulimit on the whole process is one way to
do $something, but it will just lead to a crash earlier. We somehow need to
figure out a way to limit clang's memory consumption, or guess
https://bugs.kde.org/show_bug.cgi?id=373017
Sven Brauch changed:
What|Removed |Added
CC||m...@svenbrauch.de
--- Comment #3 from Sven Brauc
https://bugs.kde.org/show_bug.cgi?id=373017
JDF changed:
What|Removed |Added
CC||dage...@free.fr
--- Comment #2 from JDF ---
The bug is s
https://bugs.kde.org/show_bug.cgi?id=373017
--- Comment #1 from gnu...@gmail.com ---
Hi,
started to test KDevelop 5.0.3 and behaviour seems to be much better now.
Only 3GB memory usage instead of >20GB! for the same large project.
Thanks for your effort!
Best,
gnux
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=373017
gnu...@gmail.com changed:
What|Removed |Added
CC||gnu...@gmail.com
--
You are receiving this m
11 matches
Mail list logo
