[framework] Memory leaks in msf3

[H D Moore]

The db_autopwn code needs to be modified to only process a specific number 
of exploit modules at once. Right now, it fires off everything at the 
same time until the list is empty, resulting in the memory use you are 
seeing. This code will be updated (soon) to have a psuedo-scheduler and a 
max concurrent exploit option. Thanks for the report!

-HD

On Tuesday 28 November 2006 13:56, nnp wrote:
> When running msf3 using db_nmap or db_autopwn with large inputs has
> anyone else gotten out of memory errors? I don't know ruby so I have
> no idea what the story with garbage collection and memory leaks is but
> here is the error.