Last modified: 2014-08-21 04:42:20 UTC
MapCacheLRU::set, when the $value passed in is an object, appears to just store a reference to $value rather than a copy of $value itself. This means that future changes to $value also affects the cached copy, which is probably not what we want in a cache.
Change 155292 had a related patch set uploaded by Wctaiwan: Set and get object copies in MapCacheLRU https://gerrit.wikimedia.org/r/155292
Based on discussions with others, the current approach appears to be the expected behaviour.
Change 155292 abandoned by Wctaiwan: Set and get object copies in MapCacheLRU Reason: Current cache behaviour seems to be expected. Bug 69789 is instead fixed with I94f06baf406afa538cd2b10139598442f9fc6759 https://gerrit.wikimedia.org/r/155292