From Patrick Hynds (repro in link above):

If you try to allocate an array with a size range between 0x027fefbd and 0x027fffec, the framework throws exceptions. This range corresponds to memory block of little under 40MB. But if allocate a buffer smaller than or larger than this range, then every thing is fine. So the following call will fail.

Byte[] test = new Byte[0x027ffc22];

It looks like there are different algorithms for big memory block allocation. Is there something special about this range?  Anyone?  Note: I'm running this on a box with 512megs.  Does this behave different on a box with more or less?

UPDATE: Until someone gives an good explaination, Dejan has added this to the .NET Bugs Registry...

A few thoughts that we open the second day of the XmlDevCon or "SellsConIV." 

• I wonder how many people here seriously debated wearing the conference T-Shirt we were given on Day 1...I thought about wearing it just because it was clean!
• Seems to me that in some way Necho is being created as a "routing" protocol...to route around Dave Winer.  Note that many years ago the real Necho was an Egyptian Lord whose goal was to reach Haran to assist the Assyrians who were under seige by Nebuchadnezzar.  Are we under seige by a Babylonian King?
• Looks like Sam Ruby can't make it to Portland.  That's a damn shame, he will be missed.  Consequently the Amazon.com fellow's VERY interesting session has been extended to include more technical details.  An unfortunate tradeoff, but the nice thing about a SellsCon is that any speaker can take their talk as deep as you'd like.