Suboptimal memory usage in ResponseAssertion

[Vladimir Sitnikov <si...@gmail.com>]

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

-- 
Regards,
Vladimir Sitnikov

Re: Suboptimal memory usage in ResponseAssertion

[sebb <se...@gmail.com>]

On 4 September 2013 23:42, Vladimir Sitnikov
<si...@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