Open raviguptasmarsh opened 4 years ago
Will you provide more details. Also provide stacktrace and logs from execution.
These screenshots are from the memory dump (scanned using MAT) taken once GC Overhead issue started. Heap size was provided as 4 gb out of which a single instance of java.lang.object[] is taking 3 GB.
The class: com.qmetry.qaf.automation.step.QAFTestStepArgumentFormatterImpl seems to be doing it:
Also, I would like to add that we are getting step not implemented exception liek this:
/**
*/
@QAFTestStep(description="verify {0} contains {1}")
public void verifyContains(String str0,String str1){
//TODO: remove NotYetImplementedException and call test steps
throw new NotYetImplementedException();
}
at multiple places now because of the way the step arguments are getting parsed now. Can this cause more memory utilization ?
@raviguptasmarsh will you try beta-3 or 4?
QAF Version
Steps To Reproduce
When running large amount of tests (regression around 3k tests ). Was not facing the issue with 2.14-RC1. Also this error is returned after the same regression tests run for 14-15 hours, which used to take 4-5 hours before switching to 3.0.0-RC3.
I am using these these properties in my maven-surefire-plugin in pom.xml
Is there anything that you recommend ?
Is the issue reproducible on runner?