[Owasp-webscarab] WebScarab Memory Leaks and Exceptions from Beanshell Scripting
Tracy, Edward [USA]
tracy_edward at bah.com
Mon May 12 14:22:17 EDT 2008
I found running some scripts for several hours started throwing non-descript
Exceptions. I traced the offending line to
I then caught and ignored the exceptions (that didn't happen on every
request), as the request and responses were still being made. Next, a long
run revealed WS slowed to a craw. Instead of sending and receiving a request
in .5seconds, it gradually slowed to 5seconds per request!
I didn't debug any further, as it would have required rebuilding a debugging
WS, and I didn't have time for that. Any thoughts? Btw, it's just an idea
that the exception is linked to the slow-down. Who knows really.
From: owasp-webscarab-bounces at lists.owasp.org
[mailto:owasp-webscarab-bounces at lists.owasp.org] On Behalf Of Rogan Dawes
Sent: Friday, May 09, 2008 11:59 AM
To: Keith Cauthen
Cc: owasp-webscarab at lists.owasp.org
Subject: Re: [Owasp-webscarab] Intermittent Listener-127.0.0.1:8008"
java.lang.OutOfMemoryError on Windows XP SP2 using WebScarab 20070504-1631
Keith Cauthen wrote:
> I was using WebScarab successfully to capture traffic last night. I
> could review the conversations and use the fuzzer. This morning, after
> restarting my laptop, I started IE7, Started WebScarab, set the lan
> Seetings to use a proxy server 127.0.0.1 port 8008, used WebScarabs
> Tools->Proxies to use the "Get IE Settings" and then clicked 'Apply'.
> When I attempted to browse to any page, such as www.msnbc.msn.com,
> the browser never responded.
> In the WebScarab Proxy Tab, Listeners Tab, I see hundreds of GETS to
> www.msnbc.msn.com:80 <http://www.msnbc.msn.com/> until I get this
> error message displayed
Your *upstream proxy* settings are broken. WebScarab allows you to set an
upstream proxy so that you can get out of a corporate firewall. There is
even a button to automatically copy these settings from IE, to make your
HOWEVER! If your IE settings are already set to point to WebScarab
(localhost:8008), you will end up in a loop, with WebScarab submitting
requests to itself, with no way of ending the loop. This causes
OutOfMemoryError's, or else something like "too many connections".
Fix your upstream proxy settings, and you will be fine.
Owasp-webscarab mailing list
Owasp-webscarab at lists.owasp.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1631 bytes
Desc: not available
Url : https://lists.owasp.org/pipermail/owasp-webscarab/attachments/20080512/b51f4aeb/attachment.bin
More information about the Owasp-webscarab