According to this API doc, which is the only source I\'ve found which describes the in-memory cache:
Chrome employs two caches — an on-disk cache and a ve
In your case I think that your problem is with the long term cache instead the in-memory cache. In the resource waterfall several requests can be marked as cached. There are various manners to avoid that if you want:
Remember to apply these rules only for the resources that you really need to. Otherwise your webserver will be overloaded with innecesary requests.
As stated in the document mentioned: in-memory cache does not apply to different page renderings even for the same url and in the same tab (in-memory cache is attached to the lifetime of a render process), so I think that does not apply for your case. Rendering cycle ends each time the page is displayed and a different one starts if rendered again. For example: when a image is loaded for the first time appears in the waterfall, but no for later requests on the same page.