Closed felipewarrener closed 7 hours ago
According to your output, there was only 1 event in queue at the time it was killed. Without seeing your debug.log
, we can't know the cause for sure. However, it's likely it's the massdns module. Massdns needs to keep track of its mutations in order to keep from trying the same ones again. This has already been fixed in BBOT 2.0 through the use of a bloom filter.
I have to ask, are these 12000 domains related in any way? I.e. do they belong to the same parent company?
Closing due to inactivity.
I woke up to my instance of bbot being killed after reaching ~9GB of memory usage:
Are there any flags where I can get memory to be free'd and results written to disk more frequently or something? This was with a list of 12,000 seed domains.