-
Bug
-
Resolution: Fixed
-
P4
-
6u5, 7u79, emb-8u26, 8
-
b04
-
sparc
-
solaris
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8054121 | emb-8u26 | Mattias Tobiasson | P4 | Closed | Won't Fix |
java/lang/management/MemoryMXBean/Pending.java
Fails with the following message:
java.lang.RuntimeException: Unexpected current number of objects pending for finalization: Current finalized = 1200 Current pending = 0 but expected > 0
Here are execution results:
http://gtee.sfbay.sun.com/gtee2.0/results/JDK6UR/PROMOTION/VM/6u5/b05/071030172457/vm/SOLSPARC5.9/client/batch/vm-SOLSPARC5.9_client_batch_MM_REGRESSION2007-10-30-17-35-34/java/lang/management/MemoryMXBean/Pending.jtr
How to reproduce:
ssh parislv.sfbay
cd <temp_dir>
/net/gtee.sfbay/export/bin/run_jtreg -suite MM_REGRESSION -test java/lang/management/MemoryMXBean/Pending.java -jdk /net/gtee/export/sqe/jdk/vm/6u5/promoted/b05 -Xbatch -XX:CompileThreshold=2
This failure mode was seen in the 2008.06.02 nightly without
the -XX:CompileThreshold option:
New MM_REGRESSION failures (from 2008.06.02)
java/lang/management/MemoryMXBean/Pending.java
java/lang/management/MemoryMXBean/PendingAllGC.sh
These tests failed due to "RuntimeException: Unexpected current
number of objects pending for finalization: Current finalized =
1200 Current pending = 0 but expected > 0" on Linux IA32 Client
VM (machine inclusion), Solaris X86 Client VM (machine
mspacman), Solaris SPARC Client VM (machine vm-t2000-01a), and
Win32 Client VM (machine vm-em64t-01).
This failure mode is covered by the following closed bug:
6625574 4/4 java/lang/management/MemoryMXBean/Pending.java
fails: "pending finalization = 0 but expected > 0"
Since these failures happened without the -XX:CompileThreshold
option, I have reopened the bug. I will copy this entry to the
bug report.
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-06-02/Serv_Baseline/javase/linux-i586/client/comp/javase-linux-i586_client_comp_MM_REGRESSION2008-06-02-19-26-12/workDir/java/lang/management/MemoryMXBean/Pending.jtr
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-06-02/Serv_Baseline/javase/solaris-i586/client/comp/javase-solaris-i586_client_comp_MM_REGRESSION2008-06-02-19-22-50/workDir/java/lang/management/MemoryMXBean/Pending.jtr
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-06-02/Serv_Baseline/javase/solaris-sparc/client/comp/javase-solaris-sparc_client_comp_MM_REGRESSION2008-06-02-19-30-19/workDir/java/lang/management/MemoryMXBean/Pending.jtr
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-06-02/Serv_Baseline/javase/windows-i586/client/comp/javase-windows-i586_client_comp_MM_REGRESSION2008-06-02-19-26-50/workDir/java/lang/management/MemoryMXBean/Pending.jtr
In this nightly, the -Xcomp option is being passed via the
JavaTest/JTREG '-vmoption'; in subsequent nightlies, we will
be switching to the new JavaTest/JTREG '-javaoption' for
passing the '-Xcomp'.
This failure mode was seen in the 2009.01.06 nightly without
the -XX:CompileThreshold option:
New MM_REGRESSION failures (from 2009.01.06)
* java/lang/management/MemoryMXBean/Pending.java
This test failed due to "RuntimeException: Unexpected current
number of objects pending for finalization: Current finalized =
1200 Current pending = 0 but expected > 0" on Linux IA32 Client
VM (machine vm-coppermine-1), Solarix X86 Client VM (machine
vm-v20z-5), Solaris SPARC Client VM (machine vm-b1600s-1) and
Win32 Client VM (machine vm-x86-3).
This failure mode is covered by the following closed bug:
6625574 4/4 java/lang/management/MemoryMXBean/Pending.java
fails: "pending finalization = 0 but expected > 0"
Since these failures happened without the -XX:CompileThreshold
option, I have reopened the bug (again). I will copy this entry
to the bug report.
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-01-06/RT_Baseline/javase/linux-i586/client/comp/linux-i586_client_comp_MM_REGRESSION/analysis.html
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-01-06/RT_Baseline/javase/solaris-i586/client/comp/solaris-i586_client_comp_MM_REGRESSION/analysis.html
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-01-06/RT_Baseline/javase/solaris-sparc/client/comp/solaris-sparc_client_comp_MM_REGRESSION/analysis.html
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-01-06/RT_Baseline/javase/windows-i586/client/comp/windows-i586_client_comp_MM_REGRESSION/analysis.html
Fails with the following message:
java.lang.RuntimeException: Unexpected current number of objects pending for finalization: Current finalized = 1200 Current pending = 0 but expected > 0
Here are execution results:
http://gtee.sfbay.sun.com/gtee2.0/results/JDK6UR/PROMOTION/VM/6u5/b05/071030172457/vm/SOLSPARC5.9/client/batch/vm-SOLSPARC5.9_client_batch_MM_REGRESSION2007-10-30-17-35-34/java/lang/management/MemoryMXBean/Pending.jtr
How to reproduce:
ssh parislv.sfbay
cd <temp_dir>
/net/gtee.sfbay/export/bin/run_jtreg -suite MM_REGRESSION -test java/lang/management/MemoryMXBean/Pending.java -jdk /net/gtee/export/sqe/jdk/vm/6u5/promoted/b05 -Xbatch -XX:CompileThreshold=2
This failure mode was seen in the 2008.06.02 nightly without
the -XX:CompileThreshold option:
New MM_REGRESSION failures (from 2008.06.02)
java/lang/management/MemoryMXBean/Pending.java
java/lang/management/MemoryMXBean/PendingAllGC.sh
These tests failed due to "RuntimeException: Unexpected current
number of objects pending for finalization: Current finalized =
1200 Current pending = 0 but expected > 0" on Linux IA32 Client
VM (machine inclusion), Solaris X86 Client VM (machine
mspacman), Solaris SPARC Client VM (machine vm-t2000-01a), and
Win32 Client VM (machine vm-em64t-01).
This failure mode is covered by the following closed bug:
6625574 4/4 java/lang/management/MemoryMXBean/Pending.java
fails: "pending finalization = 0 but expected > 0"
Since these failures happened without the -XX:CompileThreshold
option, I have reopened the bug. I will copy this entry to the
bug report.
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-06-02/Serv_Baseline/javase/linux-i586/client/comp/javase-linux-i586_client_comp_MM_REGRESSION2008-06-02-19-26-12/workDir/java/lang/management/MemoryMXBean/Pending.jtr
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-06-02/Serv_Baseline/javase/solaris-i586/client/comp/javase-solaris-i586_client_comp_MM_REGRESSION2008-06-02-19-22-50/workDir/java/lang/management/MemoryMXBean/Pending.jtr
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-06-02/Serv_Baseline/javase/solaris-sparc/client/comp/javase-solaris-sparc_client_comp_MM_REGRESSION2008-06-02-19-30-19/workDir/java/lang/management/MemoryMXBean/Pending.jtr
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2008-06-02/Serv_Baseline/javase/windows-i586/client/comp/javase-windows-i586_client_comp_MM_REGRESSION2008-06-02-19-26-50/workDir/java/lang/management/MemoryMXBean/Pending.jtr
In this nightly, the -Xcomp option is being passed via the
JavaTest/JTREG '-vmoption'; in subsequent nightlies, we will
be switching to the new JavaTest/JTREG '-javaoption' for
passing the '-Xcomp'.
This failure mode was seen in the 2009.01.06 nightly without
the -XX:CompileThreshold option:
New MM_REGRESSION failures (from 2009.01.06)
* java/lang/management/MemoryMXBean/Pending.java
This test failed due to "RuntimeException: Unexpected current
number of objects pending for finalization: Current finalized =
1200 Current pending = 0 but expected > 0" on Linux IA32 Client
VM (machine vm-coppermine-1), Solarix X86 Client VM (machine
vm-v20z-5), Solaris SPARC Client VM (machine vm-b1600s-1) and
Win32 Client VM (machine vm-x86-3).
This failure mode is covered by the following closed bug:
6625574 4/4 java/lang/management/MemoryMXBean/Pending.java
fails: "pending finalization = 0 but expected > 0"
Since these failures happened without the -XX:CompileThreshold
option, I have reopened the bug (again). I will copy this entry
to the bug report.
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-01-06/RT_Baseline/javase/linux-i586/client/comp/linux-i586_client_comp_MM_REGRESSION/analysis.html
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-01-06/RT_Baseline/javase/solaris-i586/client/comp/solaris-i586_client_comp_MM_REGRESSION/analysis.html
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-01-06/RT_Baseline/javase/solaris-sparc/client/comp/solaris-sparc_client_comp_MM_REGRESSION/analysis.html
http://sqeweb.sfbay.sun.com/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-01-06/RT_Baseline/javase/windows-i586/client/comp/windows-i586_client_comp_MM_REGRESSION/analysis.html
- backported by
-
JDK-8054121 java/lang/management/MemoryMXBean/Pending.java fails: "pending finalization = 0 but expected > 0"
-
- Closed
-