1680159 - OOM running hazard analysis on local desktop

Status: RESOLVED FIXED

(Core :: JavaScript: GC, defect, P3)

Description

[Steve Fink [:sfink] [:s:]]

I have been having trouble running the hazard analysis locally because at some point while compiling the tree and gathering info, it OOMs my computer. Which isn't pleasant.

Comment 1

[Steve Fink [:sfink] [:s:]]

It always OOMs the xsource binary, which is collecting all source code, both before and after preprocessing, into a giant database. Which is never used. (Well, I think it might get used in one place to look at the path to jsapi.h, purely to determine how many leading components to strip from the paths.)

I added an option to skip the source gathering, which enabled the hazard analysis to run locally on my machine again.

I don't actually know if I introduced a memory leak bug somewhere, or if this is just a matter of some unified source file becoming insanely large. But it would be better to stop copying around the gigabytes of data uselessly anyway.

Comment 2

[Steve Fink [:sfink] [:s:]]

Attachment: Bug 1680159 - Allow suppressing the collection of source code with $XGILL_NO_SOURCE

Comment 3

[Steve Fink [:sfink] [:s:]]

Attachment: Bug 1680159 - Do not collect source code during automated hazard analysis.

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/adb56bd07946
Do not collect source code during automated hazard analysis. r=jonco

Comment 5

[Bogdan Tara[:bogdan_tara | bogdant]]

https://hg.mozilla.org/mozilla-central/rev/adb56bd07946