Bug 18235 - System.Runtime.Caching.MemoryCache doesn't order expirable items correctly
Summary: System.Runtime.Caching.MemoryCache doesn't order expirable items correctly
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-06 19:55 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-06 19:55:50 UTC
MemoryCache expired items are not expired in the correct order. This means items can live much longer than intended by the caller. 

The issue is hidden by Get() which does an expiry check and returns null so the item appears to be expired but is still in the timedItems heap.
Comment 1 Craig Minihan 2014-03-06 20:34:51 UTC
Fixed make in pull #937
Comment 2 Craig Minihan 2014-03-25 20:14:06 UTC
Merged into master in commit: e777f9d04576ff65198c34113ca165ec8463b348