[Mono-bugs] [Bug 528833] Threadpool stress test occasionally throws TypeInitializationException

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=528833

User rkumpera at novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=528833#c1


Rodrigo Kumpera <rkumpera at novell.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rkumpera at novell.com




--- Comment #1 from Rodrigo Kumpera <rkumpera at novell.com>  2009-08-06 07:54:14 MDT ---
This is a bug on the CLR. The execution model is so damn stupid when it comes
to async exceptions and thread handling that makes me want to puke.

Thread abort is, by definition, unsafe all the time because it can break type
initializers and cause all sort of havok on the appdomain.

It's not safe even at appdomain unload time because finalizers and finally
clauses might depend on types been doomed by the abort itself.

MS has this idiotic behavior except that mono sometimes incorrectly abort
catch/finally clauses and mono doesn't support CER.

Thread::Abort is the Godzilla of your puppies threads.

We could treat .cctor's as finally regions and trigger aborts around them, this
is a sane option thou a deviation from MS behavior.

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.