{"push_id":1232265753,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"9e035c3ebf7c77f8d12b9e5cdb55dde670000321","before":"23304585f973f4d6002fb454e8fb21e89a3441da","commits":[{"sha":"9e035c3ebf7c77f8d12b9e5cdb55dde670000321","author":{"name":"Ben Manes","email":"ee0e64c9450b4df8e0b1dbf5a7a9b829c5bebc3f@gmail.com"},"message":"Null the value field when the entry is dead (evicted)\n\nIn #103 a user broke the map contract by accidentially modifying the\nkey, causing lookups to not find the entry. This includes eviction,\nwhich finds the entry on a linked list (\"Node\") and removes from the\nhash table with the stashed key. While the node can be marked as dead,\nthe removal might fail in practice if racing with an explicit\ninvalidation.\n\nWhen an weak/soft value entry is dead we already clear the reference to\nreduce the GC burden. In the common case null'ing out the field would\nhave no benefit, because the GC would trace live objects and not need\nthe hint. In the above case it reduces the impact of a memory leak by\ncollecting the heavy user objects. The node instances would still\naccumulate and the leak may take longer to fail. But since we do it for\nreference caching and it could reduce the likelihood of outages, it\ndoes seems friendlier to null the strong value field.","distinct":true,"url":"https://api.github.com/repos/ben-manes/caffeine/commits/9e035c3ebf7c77f8d12b9e5cdb55dde670000321"}]}
{"actor":{"display_login":"ben-manes"}}