Memory and Scriptrunner

[Tom Lister]

Hi

are there any known issues with using scriptrunner and memory usage?

We're getting outofmemory, and I know there could be lots of reasons, and just want to check in for scriptrunner/groovy issues. We have a lot of scripted fields and script workflow actions which will be invoked many times.

Are there any best practices for writing scripts?

[Vasiliy Zverev · Accepted solution]

First of all check if you have varialbe declare into loops. For exmple

for(Issue subtask: issue.getSubTaskObjects()){
    CustomField field = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("field name")
}

It is better to change to:

CustomField field = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("field name");
for(Issue subtask: issue.getSubTaskObjects()){   
    
}

[Vasiliy Zverev]

More - try not to use variable which used only once. For example:

IssueManager issueManager = ComponentAccessor.getIssueManager();
Issue issue = issueManager.getIssueObject()

It is better to use 

Issue issue = ComponentAccessor.getIssueManager().getIssueObject()

[Tom Lister]

Thanks Vasily, I'll check through our code