https://bugs.kde.org/show_bug.cgi?id=373017
--- Comment #5 from JDF <dage...@free.fr> --- 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 that he wants 16 threads to do the work, then only 512 MB will be given for each clang process. That looks too easy, and since I'm not inside kdevelop code (and know nothing about how clang is doing code parsing) I might be missing important things that will kill these ideas... But other solutions might exist: https://github.com/valloric/youcompleteme/issues/184 https://bugreports.qt.io/browse/QTCREATORBUG-11640 https://unix.stackexchange.com/questions/44985/limit-memory-usage-for-a-single-linux-process https://unix.stackexchange.com/questions/1424/is-there-a-way-to-limit-the-amount-of-memory-a-particular-process-can-use-in-uni https://letitknow.wordpress.com/2014/12/11/how-to-limit-memory-usage-of-a-process-under-linux/ -- You are receiving this mail because: You are watching all bug changes.
