Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
HashSet.TrimExcess() calls HashSet.Resize(), which calculates the new collection size as follows:
int newSize = HashPrimeNumbers.ToPrime ((table.Length << 1) | 1);
This causes the collection to double in size, exactly the opposite of the callers intention. The following test code shows the issue:
var lookup = new System.Collections.Generic.HashSet<string>();
for (int i = 0; i < 10000; i++)
for (int i = 0; i < 1000; i++)
In the second loop we blow when i=13 since the array sizes are now out of range.
I'm not sure HashSet.Clear() honors the spirit of the MS docs either since only the refs are released, the arrays remain the same size.
Fixed in master