JDK-8335449 : runtime/cds/DeterministicDump.java fails with File content different at byte ...
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 17,21,24
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: os_x
  • CPU: aarch64
  • Submitted: 2024-07-01
  • Updated: 2024-09-20
  • Resolved: 2024-07-08
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 17 JDK 21 JDK 23 JDK 24
17.0.14-oracleFixed 21.0.6-oracleFixed 23.0.2Fixed 24 b06Fixed
Related Reports
Relates :  
JDK-8338712 - Test runtime/cds/DeterministicDump.java fails File content different at byte #4, b0 = 96, b1 = 80
Relates :  
JDK-8241071 - Generation of classes.jsa with -Xshare:dump is not deterministic
Description
java.lang.RuntimeException: File content different at byte #4, b0 = -87, b1 = 77
	at DeterministicDump.compare(DeterministicDump.java:114)
	at DeterministicDump.doTest(DeterministicDump.java:66)
	at DeterministicDump.main(DeterministicDump.java:42)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:333)
	at java.base/java.lang.Thread.run(Thread.java:1575)
Comments
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk17u-dev/pull/2897 Date: 2024-09-19 14:19:33 +0000
19-09-2024
Fix request [17u] I backport this for parity with 17.0.14-oracle. No risk, only a test change. Clean backport. Test works as before. It is problem listed due to 8253495, which is fixed but not a candidate for backport.
19-09-2024
Fix request [21u] I backport this for parity with 21.0.6-oracle. No risk, only a test change. Clean backport. Test passes. SAP nightly testing passed.
16-09-2024
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk21u-dev/pull/977 Date: 2024-09-14 19:54:04 +0000
14-09-2024
[jdk23u-fix-request] Approval Request from sendaoYan Clean backport to make the test more robustness, test fix only, no risk.
21-08-2024
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk23u/pull/80 Date: 2024-08-21 06:32:37 +0000
21-08-2024
Looks like a test bug since JDK-8241071.
11-07-2024
Changeset: 284671a1 Author: Calvin Cheung <ccheung@openjdk.org> Date: 2024-07-08 16:44:22 +0000 URL: https://git.openjdk.org/jdk/commit/284671a1e4fb5bfe15b20b7f41fc24415b1235ed
08-07-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/20056 Date: 2024-07-05 17:29:19 +0000
05-07-2024
Regarding the following question: What part of the dump is the change actually detected in? From the map files of the two CDS archives, the crc in the headers are different: SharedArchiveFile0.map: - crc: 0xf0fdf7e2 SharedArchiveFile1.map: - crc: 0xcef5be47 It is due to their "rw" and "bm" regions are different: SharedArchiveFile0.map: ============ region ============= 0 "rw" - crc: 0xba676638 ============ region ============= 2 "bm" - crc: 0x525fe8de SharedArchiveFile1.map: ============ region ============= 0 "rw" - crc: 0x1a279a05 ============ region ============= 2 "bm" - crc: 0xacf35676
05-07-2024
CDS deterministic output is required only for building the JDK itself. During the build, G1GC is used. So this test should be make flagless so that it is not tested on flag combinations that are not required.
03-07-2024
These findings suggest either a ZGC-nonGen bug or else an assumption of CDS that does not hold with ZGC-nonGen. What part of the dump is the change actually detected in?
03-07-2024
The failure occurred mostly on macosx platforms, more reproducible on macosx-aarch64 than macosx-x64. Running the test 15 times on Oracle supported platforms with -XX:+UseZGC -XX:-ZGenerational, 13 failures on macosx-aarch64 8 failures on macosx-x64 1 failure on linux-x64 There was no failure if running with -XX:+UseZGC -XX:+ZGenerational.
03-07-2024
Seems to fail only with with -XX:+UseZGC -XX:-ZGenerational
02-07-2024
ILW=MMM=P3
02-07-2024