https://bugs.kde.org/show_bug.cgi?id=373017
--- Comment #7 from Milian Wolff <m...@milianw.de> --- @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. @JDF: Imposing a 512MB memory limit on Clang will probably lead to "OOM" kills of the parse jobs as soon as you encounter non-trivial template magic. That said, this is still the best idea so far, I think. Someone should try that out and see what happens and how clang behaves in that scenario. If a parse thread dies, we should be able to recover from that gracefully. It's certainly better than hogging up more memory than is available. So we could maybe start off by dividing the total available memory over the number of configured parse jobs and see how it goes. -- You are receiving this mail because: You are watching all bug changes.
