search for: 0b9lq1vkvmxkfqvp1cgtzm2rsdwc

...ced it was slow, so I thought "we'll need to speed things up". The build never finished. Instead, ninja crashed my machine. It turns out that each clang invocation was growing to 4Gb of RSS. All that memory is being allocated by the profile reader ( https://drive.google.com/file/d/0B9lq1VKvmXKFQVp1cGtZM2RSdWc/view?usp=sharing ). So, heads up, we need to trim it down. Perhaps by only loading one function profile at a time, use it and actively discard it. Or simply be better at flushing the reader data structures as they're used during annotations. I'll be sending patches about this in the com...

...l need to speed things up". The build never >> finished. Instead, ninja crashed my machine. >> >> It turns out that each clang invocation was growing to 4Gb of RSS. All >> that memory is being allocated by the profile reader ( >> https://drive.google.com/file/d/0B9lq1VKvmXKFQVp1cGtZM2RSdWc/view?usp=sharing >> ). >> >> So, heads up, we need to trim it down. Perhaps by only loading one >> function profile at a time, use it and actively discard it. Or simply be >> better at flushing the reader data structures as they're used during >> annotation...