-
Bug
-
Resolution: Not an Issue
-
P3
-
12
-
b03
-
x86_64
-
linux
There's an approximate 1-2MB footprint increase measured with the Footprint3-ModXFramer benchmark (using either G1 or ParallelGC). The increase is not seen with the Footprint3-ModFramer benchmark which uses AWT rather than Swing.
Footprint3-ModXFramer-G1 -2.64% (2.1MB)
Footprint3-ModXFramer-ParGC -1.84% (1.3MB)
Regressions hold into at least b4, b5, b6.
The regressions reproduces when ran on the same machine (ie, triage).
The regressions reproduces when ran on a different machine (ie, re-traige).
A JVMswap run indicates the cause is in the JDK (ie, not the JVM).
Footprint3-ModXFramer-G1 -2.64% (2.1MB)
Footprint3-ModXFramer-ParGC -1.84% (1.3MB)
Regressions hold into at least b4, b5, b6.
The regressions reproduces when ran on the same machine (ie, triage).
The regressions reproduces when ran on a different machine (ie, re-traige).
A JVMswap run indicates the cause is in the JDK (ie, not the JVM).