Re: Zenmap crashes on nmap -sL <range>/13, succeeds with <range/14>....

[Daniel Miller <bonsaiviking () gmail com>]

Steve,

Thanks for this bug report. We have recently implemented a handler for this
exception that will discard Nmap's regular output to save memory and allow
the scan to continue. This will be included in the next release.

Unfortunately, your case seems to be the smallest that we've seen trigger a
MemoryError. Can you give more information about the resources in the VM
you are using? How much memory is available?

It is expected that you will not see the memory use reach a maximum,
because the error comes when the Python interpreter attempts to grab a
large chunk of memory. At this point, the allocation fails, and the
exception gets raised, and the process's memory use never reaches the
maximum available, since the maximum is insufficient.

Dan


On Thu, Jul 17, 2014 at 12:01 PM, steven macfarlane <
steven.macfarlane () gmail com> wrote:

> nmap -sL 172.16.0.0/14 - finishes successfully
> nmap -sL 172.16.0.0/13 - crashes with error below:
>
> Version: 6.46
> Traceback (most recent call last):
>   File "zenmapGUI\ScanInterface.pyo", line 597, in verify_execution
>   File "zenmapGUI\ScanInterface.pyo", line 652, in load_from_command
>   File "zenmapCore\NmapCommand.pyo", line 352, in get_output
>   File "codecs.pyo", line 471, in read
> MemoryError
>
> This is being run on 2012R2 guest OS on top HyperV.  Watching resource
> monitor during the scan shows increased memory use but it never maxes out.
>
> Steve
> _______________________________________________
> Sent through the dev mailing list
> http://nmap.org/mailman/listinfo/dev
> Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/