[Mono-bugs] [Bug 651546] Monitor.Enter leaves orphaned locks when threads are aborted

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri Nov 5 05:42:27 EDT 2010



--- Comment #6 from Rolf Bjarne Kvinge <rkvinge at novell.com> 2010-11-05 10:42:27 CET ---
ah right, that won't unlock anything. I have no idea it's possible to throw TAE
before acquiring the lock with our JIT.

Though it is possible with MS' JIT (at least according to blog posts I've
read), and you'd have a deadlock scenario with gmcs compiled assemblies when
running them on MS' JIT.

IMHO it's better to make gmcs compile as it used to, and instead fix the
runtime bug. That way we don't run into potentially different behaviour
depending on compiler version + runtime version + MS/Mono runtime.

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

More information about the mono-bugs mailing list