| Summary: | Running a test plan that includes a CSV Data Set Config element with the Delimiter field blank causes an OutOfMemoryError | ||
|---|---|---|---|
| Product: | JMeter - Now in Github | Reporter: | Jon Schneider <jon.schneider> |
| Component: | Main | Assignee: | JMeter issues mailing list <issues> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | P2 | ||
| Version: | 2.3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Attachments: | A simple JMeter test plan with a CSV Data Set Config element with a blank Delimiter field. | ||
Fixed in SVN: URL: http://svn.apache.org/viewvc?rev=674215&view=rev Log: Bug 45185 - CSV dataset blank delimiter causes OOM This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2124 |
Created attachment 22110 [details] A simple JMeter test plan with a CSV Data Set Config element with a blank Delimiter field. In a JMeter test plan that includes a CSV Data Set Config element, if the value of the Delimiter field is cleared and then the test plan is run, an OutOfMemoryError occurs, and the JMeter GUI crashes (closes). The following error gets displayed in the console window: "Exception java.lang.OutOfMemoryError: requested 83886096 bytes for promotion. Out of swap space?" The attached test plan, BlankDelimiter.jmx, reproduces the issue. If the Delimiter field in the CSV Data Set Config element is set back to a value of ",", then the error does not occur; the test runs normally. It would be helpful if there was better error handling for this case, e.g. if the GUI could inform the user that the Delimiter field must be non-empty.