Closed Bug 1680159 Opened 2 months ago Closed 2 months ago

OOM running hazard analysis on local desktop

Categories

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

defect

Tracking

()

RESOLVED FIXED
85 Branch
Tracking Status
firefox85 --- fixed

People

(Reporter: sfink, Assigned: sfink)

Details

Attachments

(2 files)

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.

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.

Assignee: nobody → sphink
Status: NEW → ASSIGNED
Pushed by sfink@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/adb56bd07946
Do not collect source code during automated hazard analysis. r=jonco
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 85 Branch
You need to log in before you can comment on or make changes to this bug.