Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 802 [details]
Test case of the bug
I've found a deadlock in System.Web.Caching.Cache.
And while looking at the code i've found an deadlock with ReaderWriterLockSlim that doesn't apply with MS implementation.
Take two thread that share a static ReaderWriterLockSlim.
In thread one we do EnterUpgradeableReadLock
then in thread two we do : EnterWriteLock
then in thread one we do : EnterWriteLock
then there is a deadlock, all the thread are locked.
In MS implementation the thread one can enter in WriteLock because it already has the lock.
I joined a test case.
using Mono 2.10.5
Jerémie, this one looks pretty serious, can you take a look?
Hey, fixed in master and mono-2-10. Thanks for reporting!