-
Notifications
You must be signed in to change notification settings - Fork 596
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
Primitive iterator looses sync after too many elements are removed #481
Labels
Comments
@alexo134 thanks for reporting this! |
nikhilnanivadekar
added a commit
to nikhilnanivadekar/eclipse-collections
that referenced
this issue
Mar 19, 2018
…iterator().remove(). Fixes eclipse#481 Signed-off-by: Nikhil Nanivadekar <nikhil.nanivadekar@gs.com>
nikhilnanivadekar
added a commit
to nikhilnanivadekar/eclipse-collections
that referenced
this issue
Mar 19, 2018
…iterator().remove(). Fixes eclipse#481 Signed-off-by: Nikhil Nanivadekar <nikhil.nanivadekar@gs.com>
@alexo134 raised a #484 with a fix. Once merged it will be available with 9.2.0 release which is slated for 04/18: https://projects.eclipse.org/projects/technology.collections/releases/9.2.0 |
gs-rezaem
added a commit
that referenced
this issue
Mar 19, 2018
Fix PrimitiveHashSet#iterator()#remove() to not rehash. Fixes #481
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider this code:
this will cause this exception:
It works for smaller numbers of elements like max = 1k or 10k but starts to fail for 100k and more.
And I found the cause:
InternalIntIterator.remove()
calls the standard methodsIntHashSet.remove();
which does rehashing when there is too many entries occupied with sentinels.and this makes iterator invalid.
The text was updated successfully, but these errors were encountered: