JDK-8277379 : vmTestbase/gc/gctests/SoftReference/soft00X times out
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 18,19,20,21
  • Priority: P4
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: linux,windows
  • CPU: x86_64,aarch64
  • Submitted: 2021-11-18
  • Updated: 2025-05-12
  • Resolved: 2025-05-12
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 25
25Resolved
Related Reports
Relates :  
JDK-8285509 - loom: vmTestbase/gc/gctests/SoftReference/soft001/soft001.java fails with "Exception in thread "Reference Handler" java.lang.OutOfMemoryError: Java heap space"
Description
vmTestbase/gc/gctests/SoftReference/soft003/soft003.java
vmTestbase/gc/gctests/SoftReference/soft001/soft001.java

time out with serial gc after passing the test.


iteration 96
iteration 133
iteration 107
iteration 95
iteration 125
No unexpected exceptions/errors are thrown
----------System.err:(1/16)----------
STATUS:Passed.
----------rerun:(41/6426)*----------
[...]

result: Error. Program `...\jdk-18+24-1596\windows-x64.jdk\jdk-18\bin\java' timed out (timeout set to 1200000ms, elapsed time including timeout handling was 3349758ms).


test result: Error. Program `...\jdk-18+24-1596\windows-x64.jdk\jdk-18\bin\java' timed out (timeout set to 1200000ms, elapsed time including timeout handling was 3349758ms).
Comments
No reported new occurrences for a while now. I'm closing this as CNR. If we start to see timeouts with later releases in this test again I would advice that a new Bug is created and have that linked to this Bug.
12-05-2025
We've deferred this to JDK 25, but I'm going to stay vigilant and look at the timeout handler logs the next time this happens.
19-11-2024
General time out during or after the test, with different GC's.
08-04-2024
Here's a log file snippet from the jdk-20+24-1730-tier5 sighting: vmTestbase/gc/gctests/SoftReference/soft001/soft001.java #section:main ----------messages:(8/475)---------- command: main -Xbootclasspath/a:. -XX:+UnlockDiagnosticVMOptions -XX:+WhiteBoxAPI gc.gctests.SoftReference.soft001.soft001 reason: User specified action: run main/othervm -Xbootclasspath/a:. -XX:+UnlockDiagnosticVMOptions -XX:+WhiteBoxAPI gc.gctests.SoftReference.soft001.soft001 started: Tue Nov 15 01:19:50 UTC 2022 Mode: othervm [/othervm specified] Timeout information: --- Timeout information end. finished: Tue Nov 15 01:28:25 UTC 2022 elapsed time (seconds): 515.248 ----------configuration:(0/0)---------- ----------System.out:(4670/67371)---------- Stress time: 120 seconds Stress iterations factor: 1 Stress threads factor: 1 Stress runs factor: 1 Max memory: 2080374784 Sleep time: 500 Iterations: 0 Number of threads: 16 Run GC thread: false Run mem diag thread: false Run forever: false Starting Thread[#22,gc.gctests.SoftReference.soft001.soft001$Test@39107211,5,MainThreadGroup] Starting Thread[#23,gc.gctests.SoftReference.soft001.soft001$Test@9d84f65,5,MainThreadGroup] Starting Thread[#24,gc.gctests.SoftReference.soft001.soft001$Test@336224b5,5,MainThreadGroup] Starting Thread[#25,gc.gctests.SoftReference.soft001.soft001$Test@4e89b920,5,MainThreadGroup] Starting Thread[#26,gc.gctests.SoftReference.soft001.soft001$Test@170e58eb,5,MainThreadGroup] Starting Thread[#27,gc.gctests.SoftReference.soft001.soft001$Test@5ce69e08,5,MainThreadGroup] Starting Thread[#28,gc.gctests.SoftReference.soft001.soft001$Test@7e035ead,5,MainThreadGroup] Starting Thread[#29,gc.gctests.SoftReference.soft001.soft001$Test@7d40b8f4,5,MainThreadGroup] Starting Thread[#30,gc.gctests.SoftReference.soft001.soft001$Test@18ec6eb7,5,MainThreadGroup] Starting Thread[#31,gc.gctests.SoftReference.soft001.soft001$Test@7092b57c,5,MainThreadGroup] Starting Thread[#32,gc.gctests.SoftReference.soft001.soft001$Test@14806bf5,5,MainThreadGroup] Starting Thread[#33,gc.gctests.SoftReference.soft001.soft001$Test@6cfff689,5,MainThreadGroup] Starting Thread[#34,gc.gctests.SoftReference.soft001.soft001$Test@179da477,5,MainThreadGroup] Starting Thread[#35,gc.gctests.SoftReference.soft001.soft001$Test@72c1caad,5,MainThreadGroup] Starting Thread[#36,gc.gctests.SoftReference.soft001.soft001$Test@6509d8c3,5,MainThreadGroup] Starting Thread[#37,gc.gctests.SoftReference.soft001.soft001$Test@76512155,5,MainThreadGroup] iteration 0 iteration 0 iteration 0 <snip> iteration 1440 iteration 1455 iteration 1450 Timeout refired 480 times ----------System.err:(0/0)---------- ----------rerun:(37/8169)*---------- <snip> result: Error. Program `/opt/mach5/mesos/work_dir/jib-master/install/jdk-20+24-1730/linux-aarch64.jdk/jdk-20/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 515171ms).
15-11-2022
The jdk-19+28-2093-tier5 sighting: vmTestbase/gc/gctests/SoftReference/soft001/soft001.java is with G1 so perhaps this isn't a serial GC only issue...
21-06-2022