Home page logo

nmap-dev logo Nmap Development mailing list archives

RE: ZenMap Crash
From: James Rivett <JRivett () fotokem com>
Date: Fri, 28 Feb 2014 15:14:17 -0800

Thanks Daniel!  I use an 8GB RAM drive, so I will shut it off while running scans as big as I was.  

Really appreciate the reply!

Computer Support Technician
jrivett () fotokem com 
2801 W. Alameda Ave, Burbank, CA 91505
o: 818.846.3102 ext. 519 | f: 818.841.7607 | m: 818.391.3431

.********** ********** **********.
.********** **********.
.********** **********.
.********** ********** **********.

-----Original Message-----
From: Daniel Miller [mailto:bonsaiviking () gmail com] 
Sent: Friday, February 28, 2014 11:12 AM
To: James Rivett; dev () nmap org
Subject: Re: ZenMap Crash

On 02/27/2014 12:53 PM, James Rivett wrote:
Version: 6.40
Traceback (most recent call last):
   File "zenmapGUI\ScanInterface.pyo", line 557, in verify_execution
   File "zenmapGUI\ScanInterface.pyo", line 906, in refresh_nmap_output
   File "zenmapGUI\NmapOutputViewer.pyo", line 328, in refresh_output 


This error means that your computer does not have enough memory to continue. Zenmap can be a memory hog at times. You 
can try a few different things that may help:

1. Do your scan from a machine with more RAM.
2. In your zenmap.conf (on Linux: ~/.zenmap/zenmap.conf), in the [output_highlight] section, set enable_highlight = 
False 3. Do your scan with the Nmap command-line tool, then load the output into Zenmap. This will avoid a memory crash 
during scanning, but you may still have trouble viewing the output later.
4. Do smaller scans and view them separately.
5. If you have Python programming skills, audit Zenmap's memory usage and submit a patch to reduce its memory footprint.

Good luck!

Sent through the dev mailing list
Archived at http://seclists.org/nmap-dev/

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]