Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jmeter.apache.org
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 74.125.82.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAB=Je-HJ_ZwxUSZo9DBPKdXNXV4JvwFE8Dd22AqDUEDDUOpBZQ@mail.gmail.com>
References: 
 <CAB=Je-HJ_ZwxUSZo9DBPKdXNXV4JvwFE8Dd22AqDUEDDUOpBZQ@mail.gmail.com>
Date: Fri, 6 Sep 2013 15:34:02 +0100
Message-ID: 
 <CAOGo0VZ0HKonJopfS0qk3K4DZyuXYCkpM+1MLJp=0FJvPNjt1Q@mail.gmail.com>
Subject: Re: Suboptimal memory usage in ResponseAssertion
From: sebb <sebbaz@gmail.com>
To: dev@jmeter.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 4 September 2013 23:42, Vladimir Sitnikov
<sitnikov.vladimir@gmail.com> wrote:
> Hi,
>
> I've noticed that ResponseAssertion does not cleanup regex matcher memory,
> thus it keeps the whole web page in memory.
>
> RegexExtractor calls JMeterUtils.clearMatcherMemory(matcher, pattern); to
> clean up the memory.
>
> Does is make sense to add the same cleanup to ResponseAssertion?
> Same for HTTPSamplerBase -> downloadPageResources -> localMatcher

Seems like it would be good to look at making such changes.

Bugs and enhancement requests are normally done through Bugzilla, as
it's much easier to track progress there.

Would you be able to create Bugzilla requests for your suggested fixes?
Patches welcome too, but not essential here as it should be obvious
what to change.

> --
> Regards,
> Vladimir Sitnikov