Closed GoogleCodeExporter closed 9 years ago
Thanks for reporting this.
What had you done in ZAP prior to the problem?
Ie were you spidering or active scanning?
Was it a very big site?
Did you access any very large files, eg pdfs or video files?
From the log the vm_args: -Xmx512m -XX:PermSize=256M look much smaller than I
would have expected.
I'm pretty sure theres a way to increase those via a config file - I'll have a
look into this.
Original comment by psii...@gmail.com
on 19 Feb 2013 at 9:46
I did a bit of spidering. only let it run for 10-15 sec just to get some places
to start. and 4-5 active scans on specific parameters.
Original comment by flyingpo...@yahoo.com
on 19 Feb 2013 at 10:57
Would you mind provide ZAP's log file? it might contain useful information
(file zap.log located in ZAP's default directory [1]).
[1] https://code.google.com/p/zaproxy/wiki/FAQconfig
Original comment by THC...@gmail.com
on 19 Feb 2013 at 11:58
no. i run a script that checks for and deletes it securely, to protect against
sensitive data from building up. the log provided in the first post is the most
i can give you.
Original comment by flyingpo...@yahoo.com
on 19 Feb 2013 at 2:11
here are my configs... maybe helps? password: OWASPzap
Original comment by flyingpo...@yahoo.com
on 19 Feb 2013 at 2:21
Attachments:
OK. Can you, consistently, reproduce the issue? if so, would you mind to check
the log file to see if there's any exception logged?
The configurations seems normal to me.
P.S. Not likely an issue but you may want to generate a new Root CA certificate
as the configuration file contains ZAP's Root CA certificate.
Original comment by THC...@gmail.com
on 19 Feb 2013 at 11:30
ok thank you
Original comment by flyingpo...@yahoo.com
on 20 Feb 2013 at 5:20
as for reproducing, it happened when it started up. it starts fine now. im not
sure what conditions it would take to reproduce the issue sense i didn't do
anything specifically in that session. it must have been the session before
(which i discribed as well as i could above)
Original comment by flyingpo...@yahoo.com
on 20 Feb 2013 at 5:24
OK. Thanks.
Now that you mention that it happened at start up it makes more sense that the
thread stack doesn't contain ZAP's frames only VM and native frames. Probably
this was an issue between the VM and the system.
Original comment by THC...@gmail.com
on 25 Feb 2013 at 5:18
I'll close this, but please let us know if you experience this again.
Original comment by psii...@gmail.com
on 26 Feb 2014 at 1:34
Original issue reported on code.google.com by
flyingpo...@yahoo.com
on 19 Feb 2013 at 9:03Attachments: