From e8fd5b69b052e6d60710d09ba7ac5367ac9fe570 Mon Sep 17 00:00:00 2001 From: fyodor Date: Tue, 27 Jul 2010 17:50:17 +0000 Subject: [PATCH] add more results of testing with giant scan logs --- todo/nmap.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/todo/nmap.txt b/todo/nmap.txt index 46cff1e65..42f34d383 100644 --- a/todo/nmap.txt +++ b/todo/nmap.txt @@ -41,8 +41,11 @@ o [Zenmap] Consider a memory usage audit. This thread includes a claim Nmap survey respondants complained about this too. Note: Fyodor has a 50MB scan log file named ms-vscan.xml which demonstrates this problem. When trying to load the file, Zenmap - grows to 1150MB of RAM, pegs the CPU usage at 100% for 5+ - minutes (still hasn't opened the file yet). + grows to 1150MB of RAM, pegs the CPU usage at 100% for many + minutes or maybe hours (I forgot about it, but woke up the next day + to find that it had started, was then using 2.4GB of RAM. The + hosts/services functionality seemed to work, although it would take + a minute or so to switch from say "ftp" port to view "ssh" ports. o [NSE] Investigate sslv2.nse falsely reporting SSLv2 as being supported.