[llvm-dev] Elves, Orcs, and the Memory Growth

Alex Denisov via llvm-dev llvm-dev at lists.llvm.org
Wed Nov 15 13:08:50 PST 2017

Hi folks,

I have an issue with constant memory growth on Linux.
Here is what I do (real code is here[1]):

for (auto &module : modules) {
  auto owningObject = orcCompiler.compileModule(module);

After each compilation of a module memory grows by N megabytes, which is fine and expected.
The problem that the owningObject does not escape the scope, and I expect memory to be freed after each loop iteration.
It works as expected on macOS: memory spikes when we enter the loop body but gets back after we leave the body.
However, on Linux, it grows constantly and eventually exceeds all capacities.

The questions are: what can I do about it? What could hold the memory allocated for each object file? Why is it different between macOS and Linux? Who is the guilty here: the Elf or the Orc?

For your info: I use Orc APIs from LLVM 3.9.
Please let me know if I can provide more relevant information.

I would appreciate any hints and ideas on how to nail the problem down.

[1] https://github.com/mull-project/mull/blob/disable_inmemory_cache/lib/Driver.cpp#L231


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 529 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171115/fb003cba/attachment.sig>

More information about the llvm-dev mailing list