You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by David Bronner <db...@google.com> on 2006/02/11 00:35:32 UTC
Out of memory errors with no delimiter in CSV data set config
Hi all,
Maybe this is a known bug, but I couldn't find any mention of it...if you
ommit a delimiter in the CSV data set config element, it seems that JMeter
starts using enormous amounts of memory (2G for 5 threads, 1 aggregate
listener, and one HTTP sampler). I don't know why this is the case, but
several test runs without a delimiter ran out of memory and several test
runs with a comma delimiter ran OK. Hope this help someone else avoid
confusion.
-Dave
Re: Out of memory errors with no delimiter in CSV data set config
Posted by sebb <se...@gmail.com>.
As far as I know, no-one else has reported this behaviour.
Sounds as though you have found a bug, so please could you file a
Bugzilla issue for it?
It would be helpful to know:
* which version of JMeter are you using?
* version of Java and OS?
* any messages in jmeter.log
* ideally a sample test plan that shows the problem.
Thanks!
On 10/02/06, David Bronner <db...@google.com> wrote:
> Hi all,
>
> Maybe this is a known bug, but I couldn't find any mention of it...if you
> ommit a delimiter in the CSV data set config element, it seems that JMeter
> starts using enormous amounts of memory (2G for 5 threads, 1 aggregate
> listener, and one HTTP sampler). I don't know why this is the case, but
> several test runs without a delimiter ran out of memory and several test
> runs with a comma delimiter ran OK. Hope this help someone else avoid
> confusion.
>
> -Dave
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org