Re: Zenmap Crashing and CPU Utilisation hangs at 50%

[Ray Middleton <ray.middleton () gmail com>]

I tried the latest development release
nmap-5.36TEST3-setup.exe<http://nmap.org/dist/nmap-5.36TEST3-setup.exe>but
it still crashes out for me when doing big scans.  If this is not what
you mean by r21875 could you point me in the right direction to find it?

I have noticed with this release it is using more CPU power, spiking up to
60-80% but eventually coming back to 50% where it is hanging and not
responding.

On 20 January 2011 14:54, Rob Nicholls <robert () robnicholls co uk> wrote:

> On Wed, 19 Jan 2011 10:39:05 -0800, David Fifield wrote:
>
> > On Wed, Jan 19, 2011 at 10:23:01AM +0000, Rob Nicholls wrote:
> >
> > > On Tue, 18 Jan 2011 22:22:59 -0800, David Fifield wrote:
> > > > Guys, I think this is greatly ameliorated in r21861. Please give it a
> > > > try. I made it update the text field incrementally, and also apply
> > > > new
> > > > highlighting incrementally. I can "nmap --packet-trace -p- localhost"
> > > > without much delay, with highlighting on.
> > >
> > > I'm guessing you might not have tested the new incremental update
> > > code on Windows (it works as before/expected on Linux), as I don't
> > > get to see any scan results until the entire scan has completed. The
> > > highlighting seems to work fine though (from memory it looks
> > > identical to before), and it didn't freeze/crash.
> >
> > You're right, I didn't test it on Windows. It didn't work for me either
> > when I tried it. I did something different in r21875, please try it.
>
> It appears to be working much better on Windows, many thanks for fixing
> this!
>
> I'm now able to complete a -p- scan with --packet-trace (using the same
> host where Zenmap would freeze before). The CPU usage tends to briefly spike
> as updates are made, and roughly doubles with highlighting enabled (towards
> the end it was briefly maxing out one of my cores during the spikes), but
> unless you're using --packet-trace it's probably now fine for most systems
> to handle.
>
> Rob
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/