Description Alvaro Sanchez-Leon 2014-04-16 15:42:49 EDT

Currently the memory cache is built from block requests associated to a IMemoryDMContext. 

So when stop / resume events arrive the IMemoryContext is read and the corresponding entry in the cache is reset.

However, there can be child memory contexts in the form of IMemorySpaceDMContext, representing a memory space within a parent IMemoryDMContext. 
These memory space cache contexts will never be reset as only the parent IMemoryDMContext can be present in a suspend/resume event.

See e.g. eventDispatched(IResumedDMEvent e)

A proposed solution is to loop through all available context and reset its cache  if the IMemoryContext received in the event is an ancestor(parent) context.