Just noticed this on Stefano Demiliani's blog, lots and lots of bugs, some of them pretty interesting! I don't know just how 'verified' lots of them actually are:

An interesting idea of Dejan Jelovic. This page represents a registry of known .NET bugs. You can use it to see if the strange thing you are seeing is a known bug, or to report a new bug that you just found.

Known .NET Bugs

IDDescriptionProbability*Severity*Fixed
1

Form refuses to close
If a form A contains control B that contains control C that contains control D, and D is removed while it has the focus, the user won't be able to close the form. Details.

HighHigh1.1
2SoapFormatter and BinaryFormatter don't serialize some object graphs properly
If three or more classes have the same name but are in different namespaces, are part of the same hierarchy, and contain variables that have the same name, they will not be serialized properly. Details.
LowHigh1.1
3Text in the Windows Forms combo box cannot be selected using the mouse
Mouse selection simply does not work in a Windows Forms combo box. Details.
HighLow1.1
4Arrays of structures that implement ISerializable do not deserialize correctly
Details.
HighHigh1.1
5

Windows.Identity doesn't work under Windows 98
On Windows 98, You cannot use the Windows.Identity to retrieve the user login name, it returns a system level token and a null user name is returned when you access the .Name Property. Details.

LowMediumNo
6

C# optimizer produces bad code when a try-finally block is inside if-else
If a try-finally block is the last thing inside the if block of an if-else statement, the code inside the else block is always executed when compiling in Release mode. Details.

HighHigh1.1
7

Structs within structs cannot be deserialized
If you have a struct A inside struct B, and If a struct A is inside struct B which is inside object C, deserializing is going to throw a SerializationException.  Details.

MediumLow1.1
8

Problems removing an ActiveX control from its parent
If an ActiveX control is removed from its parent, any action that makes the parent invisible, such as closing the form on which it is on, throws an exception.  Details.

MediumHigh1.1
9

Font.GdiCharSet hardcoded to 1
The property GdiCharSet of the font class is hard-coded to 1.  Details.

LowLowNo
10

.NET Runtime leaks large chunks of memory
If you allocate a block of memory larger than some treshold, the .NET garbage collector will never reclaim it. Details.

HighHigh1.1
11

Instances of NumericUpDown and DomainUpDown are leaked
It seems that the NumericUpDown and DomainUpDown controls forget to remove a listener to a global event, thus always staying locked in memory. Details.

HighHighNo
12

SoapFormatter chokes on some strings
It seems SoapFormatter cannot handle strings that contain characters in the range 0x01 - 0x1f. Details.

HighHighNo
13

FileStream becomes unusable when writing to a removable drive
When writing to a FileStream on a removable drive, and the FileStream gets out of space, it sometimes gets in a state where no other method can be called on the stream, not even Dispose. Details.

MediumMediumNo
14

Mixed-mode assemblies can deadlock
C++ .NET apps can deadlock on startup. Details.

LowHighNo
15

ComboBox Data Binding Bug
ComboBox doesn't update the data through data binding when its style is set to DropDownList. Details.

MediumMediumNo
16

Each Windows Form leaks two GDI handles
Details.

HighHighNo
17

Alocation fails for certain sizes
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. Details.

MediumHighNo
18

No way to access Environment.HasShutDownStarted
This property is not static even though it should be.

LowLow1.1
19

Thread.Abort cannot abort suspended threads
If a thread is suspended, trying to abort will not work and the CPU will be pegged to 100 percent. Details.

LowHighNo
20

Control.Width and Height are silently truncated to 32,767
If you attempt to set a control's Width or Height property to a number larger than 32,767 it will be truncated. Details.

LowLowNo
21

ListView.Cursor set property has no effect.
Details.

LowLowNo
22

RegistryKey.SetValue does not store large integers as DWORD
Call RegistryKey.SetValue with an integer over 2,147,483,647 will result in the value being stored as string, and not as a DWORD. Details.

LowMediumNo

* Probability represents the probability that you will encounter this bug. Severity measures how much the bug hurts when it happens.

Do you know other bugs?