Details
-
Bug
-
Resolution: Tracked Elsewhere
-
High
-
4.4.2
-
4.04
-
Description
this has been moved across to JDOG to try and get it fixed in 5.0. it could be backported to branch if that is not too risky
If a plugin developer registers an own CustomFieldSearcher and implements getSorter, the returned LuceneFieldSorter is being cached by Lucene. This cache isn't cleared when the plugin reloads, which causes a memory leak.
In addition to that, if the custom field is part of the issue navigator configuration, the old sorter from the dead classloader is used and can cause errors similar to this, breaking the issue nav:
An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.jira.issue.fields.layout.column.ColumnLayoutItemImpl