]
Rob Stryker commented on JBIDE-20748:
-------------------------------------
Awesome catch [~dgolovin]. I've definitely seen this bug before but had absolutely no
idea what was causing it. I did get as far as finding out it was an error thrown by the
timsort implementation, but had no idea how to fix it. I've linked a new PR for it
also.
"Comparison method violates its general contract!" in JMX
memory monitor view
-----------------------------------------------------------------------------
Key: JBIDE-20748
URL:
https://issues.jboss.org/browse/JBIDE-20748
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx
Affects Versions: 4.3.0.CR1
Reporter: Denis Golovin
Assignee: Denis Golovin
Priority: Critical
Fix For: 4.3.1.Final, 4.4.0.Alpha1
{code}Workaround for comparator violation:
- set system property java.util.Arrays.useLegacyMergeSort=true
- use a 1.6 JRE
message: Comparison method violates its general contract!
this: org.jboss.tools.jmx.jvmmonitor.internal.ui.properties.memory.HeapComparator
comparator: null
{code}