Skip to content
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.

Harden trigger and callback registrations in CacheEntry #17

Closed
Tratcher opened this issue Sep 16, 2014 · 2 comments
Closed

Harden trigger and callback registrations in CacheEntry #17

Tratcher opened this issue Sep 16, 2014 · 2 comments
Assignees
@BrennanConroy
Labels
3 - Done bug
Milestone
1.0.0-rc2

Comments

@Tratcher
Copy link
Member

There are possible race conditions in CacheEntry between AttachTriggers and DetatchTriggers. Similar for the callback APIs. These need to be hardened to prevent potential stress/race crashes.
@Tratcher Tratcher self-assigned this Sep 16, 2014
@Tratcher Tratcher removed their assignment Oct 9, 2014
@muratg muratg added this to the 1.0.0 backlog milestone Jul 16, 2015
@muratg muratg modified the milestones: 1.0.0-rc2, 1.0.0 backlog Nov 18, 2015
@BrennanConroy BrennanConroy mentioned this issue Nov 24, 2015
Merged
@BrennanConroy
Copy link
Member

Every call to InvokeEvictionCallbacks is wrapped in the ReaderWriterLock in MemoryCache so it looks impossible to invoke more than once

@BrennanConroy BrennanConroy mentioned this issue Dec 16, 2015
Merged
@BrennanConroy
Copy link
Member

#126 and #132

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@BrennanConroy BrennanConroy

Labels
3 - Done bug
Projects
None yet
Milestone
1.0.0-rc2
Development

No branches or pull requests
3 participants
@muratg @Tratcher @BrennanConroy