Bug 18245 - System.Runtime.MemoryCache.GetValues() throws LockRecursionException with expired items
Summary: System.Runtime.MemoryCache.GetValues() throws LockRecursionException with exp...
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web ()
Version: master
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2014-03-07 07:12 UTC by Craig Minihan
Modified: 2014-07-30 11:18 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Craig Minihan 2014-03-07 07:12:31 UTC
System.Runtime.MemoryCache.GetValues(IEnumerable <string>) will cause a LockRecursionException if the cache contains expired items.

The scenario is:
* the polling interval is high, say 10s
* items are added with a short lifespan
* calling GetValues() results in a call to MemoryCacheContainer.GetEntry() which does an EnterReadLock() on the cache
* assuming the item is still in the cache then ExpireIfNeeded() is called which does an EnterWriteLock() - and we get an     exception

MemoryCacheContainer.Get() does an EnterUpgradeableReadLock() - and this is the fix in this case.
Comment 1 Craig Minihan 2014-03-07 07:53:51 UTC
Fix made in pull #938
Comment 2 Craig Minihan 2014-03-25 20:14:47 UTC
Merged into master in: a678a101ee746e0c8f89f8e67c4a668d2af45d14