JDK-8373701 : [lworld] Revert Use Objects.equals in HashMap and ConcurrentHashmap
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.lang
  • Affected Version: repo-valhalla
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2025-12-15
  • Updated: 2025-12-15
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.
Other
repo-valhallaUnresolved
Related Reports
Causes :  
Description
Revert the use of Objects.equals to the previous explicit `==` check for identity and conditional call to .equals.
The use of Objects.equals (without identity) caused classes with poorly written .equals methods to work incorrectly with HashMap and ConcurrentHashmap.

A discussion of the broader issue is in JDK-8373558.

The specific failure was: JDK-8373466 [world] javax.xml TransformerTest fails after change to HashMap