Skip to content
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

Jump to bottom

NPE in merged method call of immutable.HashMap.HashMap1 when kv field of HashMap1 is null #9688

Closed
scabug opened this issue Mar 7, 2016 · 2 comments
Closed

NPE in merged method call of immutable.HashMap.HashMap1 when kv field of HashMap1 is null #9688

scabug opened this issue Mar 7, 2016 · 2 comments
Assignees
@lgieron
Milestone
2.11.11

Comments

@scabug
Copy link

scabug commented Mar 7, 2016

Calling a merged method on scala.collection.immutable.HashMap.HashMap1 object whose kv is null throws a NullPointerException. Normally, the kv field of HashMap1 object is set (or is lazily initialized with ensurePair call before it is actually used) but it is possible for it to be null - one case I know of is when a HashMap1 object is deserialized.
@scabug
Copy link
Author

scabug commented Mar 7, 2016

Imported From: https://issues.scala-lang.org/browse/SI-9688?orig=1
Reporter: @lgieron
Affected Versions: 2.11.7

@scabug
Copy link
Author

scabug commented Mar 7, 2016

@lgieron said:
I've created a pull requests which fixes this:
scala/scala#5017

@scabug scabug closed this as completed May 23, 2016
@scabug scabug added the critical label Apr 7, 2017
@scabug scabug added this to the 2.11.9 milestone Apr 7, 2017
@scabug scabug mentioned this issue Apr 7, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lgieron lgieron

Labels
None yet
Projects
None yet
Milestone
2.11.11
Development

No branches or pull requests
2 participants
@lgieron @scabug