Hi Jamie Echlin,
I encountered an Out Of Memery issue at our JIRA instance with Script Runner plugin. I analyze the heap dump by Eclipse Memory Analyzer, and the result is that:
One object nearly (class name is com.atlassian.jira.jql.operand.registty.LazyResettableJqlFunctionHandlerRegistry )retained all the PS Old Gen heap and can't be recovered by GC.
You can refer to following image for the details.
I want to know that what operation will call this class and why this memory was not been recovered?
JVM Input Arguments:
-Dcatalina.base=/data/tomcat/jira -Dcatalina.home=/data/tomcat/jira/software/tomcat -Djava.io.tmpdir=/data/tomcat/jira/tmp -Djavax.net.ssl.keyStore=/data/tomcat/jira/SSL/jiracerts -Djavax.net.ssl.trustStore=/data/tomcat/jira/SSL/jiracerts -Djavax.net.ssl.keyStorePassword=changeit -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dfile.encoding=utf-8 -Dmail.mime.decodeparameters=true -Dnon.admin.upgrade=true -XX:MaxPermSize=1024m -Djira.jelly.on=true -Xms7072m -Xmx7072m -verbose -Dcommons.daemon.process.id=17664 -Dcommons.daemon.process.parent=17663 -Dcommons.daemon.version=1.0.10 abort
It could be any type of code. The images you have above seem to imply the script runner is running some JQL which is leaking memory. What JQL it is running is up to you and your scripts or the built in functions - you've issued a JQL query somewhere that is not suitable. If it's happening regularly, it's probably a saved filter that someone keeps using. Or a script you've written.
Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the 104 years logged in 2017 , and we aren’t even through December yet....
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs