issueFieldMatch (and probably others) can cause OoM
*This issue has moved*
This issue has been moved permanently to Adaptavist's Product Support JIRA instance.
All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the
Can't access your account link in order to reset to a new password.
if used with an empty filter query, or filter query that returns a very large number of issues, and if the size of an issue in the index is very large.
Some functions only require access to certain fields and those fields are known in advance... so a Lucene collector could maybe be used to load only those fields.
Simpler, the filter query loads everything, whereas it should page the results to the next filter.
OK... that's somewhat surprising. The paging is in 3.0.10. There are further performance improvements that can be made to that, in the next tranche of development work. However, yes, you can disable it in .11.
Hi Jamie, I tested 3.0.10 and the problem was still there. Haven't had a chance to try out 3.0.11 yet till we update our JIRA version but will once we do.
- what version of the plugin are you using? Recent versions use paging and should have relatively constant memory.
In the latest version you can disable any function: https://jamieechlin.atlassian.net/wiki/display/GRV/ScriptRunner+3.0.11
We also experienced this when a user placed this search:
issueFunction in issueFieldMatch("", labels, "xyz-*")
Our system struggled for 1.5 hours taking CPU cycles collecting garbage, but recovered eventually. I was hoping to figure out how to disable this JQL function via the steps describe in but seems we'll have to wait for version 3.0.11 after we upgrade JIRA.
I have a fixed version that I would be grateful if you could test in your staging instance - it's available from https://jamieechlin.atlassian.net/wiki/download/attachments/1212418/groovyrunner-3.0.6-SNAPSHOT.jar?api=v2
Let me know.