OutOfMemoryError: Java heap space while spidering a large site
Open
Nobody has claimed this yet.
add-on
bug
in:spider
Usability
- Dominant language
- Java
- Stars
- 15.8k
- Forks
- 2.6k
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 17
Description
Hi,
I have quite a large site (broadvision technology).
While spidering, ZAp collects more than 120K URI and finished the heap.
Thanks for your attention
Maurizio
Original issue reported on code.google.com by MaurizioPastore60 on 2014-08-04 09:36:32
- Attachment: OWASP ZAP.zip
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the original report and the attached OWASP ZAP.zip, then reproduce spidering a large site that collects more than 120K URIs. Trace where heap usage grows during spidering and define done as completing the crawl without an OutOfMemoryError, with regression coverage for the large-site case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100