84517 2012-04-20 17:34:51 -0700 ASSERT(revalidatingResource->inCache()) failure in MemoryCache::revalidationSucceeded() 2012-10-17 13:00:05 -0700 1 1 1 Unclassified WebKit Page Loading 528+ (Nightly build) Unspecified Unspecified RESOLVED WORKSFORME P2 Normal --- 66687 1 wangxianzhu webkit-unassigned abarth ap beidson japhet koivisto martijn oldest_to_newest 607098 0 wangxianzhu 2012-04-20 17:34:51 -0700 Encountered this on chromium-android by repeatedly openning new tabs, closing tabs, reloading tabs, switching between tabs, etc. The reason seems: MemoryCache::clear() might be called on low memory condition during a resource revalidation, causing the resources to be evicted, then some ASSERTs in MemoryCache::revalidationSucceeded() may fail: ASSERT(revalidatingResource->inCache()); ASSERT(!m_resources.get(resource->url())); // There might be another revalidating or revalidated resource after the original revalidation is evicted. 620096 1 abarth 2012-05-09 17:32:03 -0700 So, the ASSERT is wrong and should be removed? 620110 2 wangxianzhu 2012-05-09 17:41:34 -0700 I think the ASSERTs are useful in most cases. Perhaps we need some logic to handle the low memory eviction case, e.g. to prevent revalidating resources from being evicted. 744525 3 abarth 2012-10-17 13:00:05 -0700 This appears to have been resolved in some other way.