-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8358624: ImmutableDescriptor violates equals/hashCode contract after deserialization #25758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
8358624: ImmutableDescriptor violates equals/hashCode contract after deserialization #25758
Conversation
👋 Welcome back kevinw! A progress list of the required criteria for merging this PR into |
❗ This change is not yet ready to be integrated. |
@kevinjwalls The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
…Descriptor_hashcode
@@ -138,6 +138,7 @@ private Object readResolve() throws InvalidObjectException { | |||
if (names == null || values == null || names.length != values.length) | |||
bad = true; | |||
if (!bad) { | |||
hashCode = -1; // Force recalculation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Would it make sense to add same comment to the lines: 445, 452,473, 493?
I'm not much of a serialization expert, so just asking for some clarification here. I assume when de-serialized, the initial hashcode is always 0. Why it is 0 and not by default -1. Seems this would be an issue with any de-serialized type and all would need to explicitly set to -1 as you have done in this case. |
Hashcode needs to be reset to -1 to force its recalculation on next call, after deserialization.
The change in the readResolve() method is the fix for this problem. While here I added similar lines in other methods that may update fields (although these are noted as not supported, as they change a class supposedly "immutable").
Added a test. There is a test for serialization for this class, but I found it clearer to add the test for this specific recently discovered issue in its own test file.
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25758/head:pull/25758
$ git checkout pull/25758
Update a local copy of the PR:
$ git checkout pull/25758
$ git pull https://git.openjdk.org/jdk.git pull/25758/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25758
View PR using the GUI difftool:
$ git pr show -t 25758
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25758.diff
Using Webrev
Link to Webrev Comment