cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-2951) FreeableMemory can be accessed after it is invalid
Date Tue, 26 Jul 2011 22:03:10 GMT
FreeableMemory can be accessed after it is invalid

                 Key: CASSANDRA-2951
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 0.8.0
            Reporter: Jonathan Ellis
            Assignee: Jonathan Ellis
            Priority: Minor
             Fix For: 0.8.3
         Attachments: 2951.txt

SerializingCache.get looks like this:

    public V get(Object key)
        FreeableMemory mem = map.get(key);
        if (mem == null)
            return null;
        return deserialize(mem);

If a cache object is evicted or replaced after the get happens, but before deserialize completes,
we will trigger an assertion failure (if asserts are enabled) or segfault (if they are not).

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message