App data retriever memory leak - Blows up scraping scraping app data.

[AdamSlack]

Retriever fetches over 500k search terms and then collects 120 sets of app data for each search term. JS then ran out of memory. Rip.

[AdamSlack]

fixed, doing it a search term at a time now. donezo.

[AdamSlack]

Promises not releasing memory. What is life.

[sauyon]

incredible

[AdamSlack]

potentially narrowed down to two things.

One:
However i'm going over all search terms in the DB is leading to there being one massive long promise chain that mean the GC can't do its job. I've tried doing it a couple of ways now. each of them lead to mem leak.

Two:
The promises aren't actually the issue and its the db.js causing the issues. the pooling for postgres client connections might not be releasing properly when complete. I think its more likely to be One though.