Bug 16318 - List<T> initializes to different size than Microsoft compiled CIL
Summary: List<T> initializes to different size than Microsoft compiled CIL
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: 3.2.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2013-11-18 12:28 UTC by Stephen Rawlins
Modified: 2013-11-29 14:40 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description Stephen Rawlins 2013-11-18 12:28:56 UTC
The following test passes on Microsoft Windows/Visual Studio, but fails on Mac/Xamarin/Mono implementation:

[Test]
public void ItemsCollectionCapacity()
{
	string[] input = { "Brachiosaurus", 
          "Amargasaurus", 
          "Mamenchisaurus" };

	List<string> dinosaurs = new List<string>(input);
	Assert.AreEqual(3, dinosaurs.Capacity);
}


On the Xamarin/Mono execution, the initial capacity is 4 (vs. 3 on Windows).

It appears that Windows sets the initial collection's capacity to 3 (based on the 3-element input supplied with the constructor call), whereas Xamarin appears to first allocate the "()" (empty constructor) List - which sets initial capacity at 2 - and subsequently grows by doubling, so the 3rd element bumps capacity up to 4.

When executed on Xamarin/Mono, the test fails with:

  Expected: 3
  But was: 4 

This difference causes cross-platform testing to fail.
Comment 1 Marek Safar 2013-11-29 14:40:59 UTC
Fixed in master