High CPU utilization and/or Out Of Memory errors

Symptoms

Unusual latency with one or more nodes;

CPU spikes;

Out Of Memory errors;

Examining the high-CPU threads from the thread dump you can see the following stack trace:

java.util.HashMap$TreeNode.balanceInsertion(HashMap.java:2234)
java.util.HashMap$TreeNode.treeify(HashMap.java:1943)
java.util.HashMap$TreeNode.split(HashMap.java:2175)
java.util.HashMap.resize(HashMap.java:714)
java.util.HashMap.putVal(HashMap.java:663)
java.util.HashMap.put(HashMap.java:612)
java.util.HashSet.add(HashSet.java:220)
com.jiraeditor.jeditor.renderer.JEditorRendererPlugin.render(JEditorRendererPlugin.java:142)

Cause

The problem is caused by a bug in JEditor.

The bug exists in the following version range: 3.0.17 - 3.2.1.

How to solve

Upgrade to JEditor 3.2.2 or higher.

The CPU usage should start normalizing immediately.

Please note: In the event of a plugin change or upgrade, Jira does not scan for existing threads using plugin code. The threads running the code from the old version may survive the upgrade and continue utilizing CPU/memory.

We suggest monitoring CPU and memory utilization for 24 hours following the upgrade. You may need to restart Jira nodes where the problem persists.