"Waiting for cache" error
We might have noticed when visiting Slashdot and Digg the pages would never get loaded completely and instead there would be a small message in the status area that appears to us at the bottom of the window where the link text appears saying "waiting for cache". The same pages will definitely load fine in Firefox Web browser. The websites you are being affected by might be different from others.
After some web searches made in the browser it appears to us as some sort of cache corruption issues have happened, and the simplest way to get rid of it is to clear the cache and restart the browser.
Clearing Google Chrome's Cache
To clear the cache in Google Chrome click on the small spanner icon at the top right of the application window on the home page of the browser. This is shown in the screenshot below with the top red arrow pointing to the spanner icon. The menu below appears when you click it. Next click the "Clear browsing data" button.
The "Clear Browsing Data" dialog will then appear as shown in the screenshot below. Most of the options will likely be checked so, uncheck the ones you don't want to clear. In the example below I've only left the "Empty the Cache" option checked. You can then choose to clear data from just the last day, the last week, last 4 weeks or everything from the drop down box. You want to clear everything.
Finally, click the "Clear Browsing Data" button and, as a precaution, restart the browser and you'll have a nice clean cache and the error message should have gone away.
IE calls the cache "temporary internet files", and the cache (temporary files) is used to speed up the rendering of web pages on subsequent visits to a site (or even viewing other pages within the same site within the same visit in some instances). Because the relevant files are already saved (cached) on your computer, it doesn't take pages as long to render because the instruction to fetch page X from the server doesn't have to go off to the server and then wait for all the components to be downloaded from the server to your computer before the page loads. Caching reduces the load on busy servers, and the amount of time you're hanging around waiting for a page to load. You may have noticed that after you've cleared the cache, some pages, and particularly images on pages, can take longer to load the first time you visit a particular page, particularly on older, slower computers.
For web developers, the main use of clearing the cache is after making changes to ensure that they're not seeing an "old" version of a page, and that any changes they've made have taken effect properly. Web developers can also affect whether a browser will cache a page by altering a page's meta tags to instruct browsers either not to cache a page at all, or to only cache a page for a certain length of time. It's usually used for time sensitive information where a page's content may change rapidly, and if a page was cached the user could be viewing "old" information if it was cached.
Most browsers unfortunately not Chrome quite just yet though give you an option of specifying how much space on a machine should be used for the cache, so you can specify how much space you want to use for temporary files. IIRC IE recommends setting it at between 50 and 250 MB. Also with IE you can specify how often you want IE to check for a new version of a page, and set it to "never" if you don't want the browser to cache anything, but that will slow down your browsing experience, because each time your computer sends a request to a server for a page, every element of that page will have to be downloaded from the server again.
If you want a utility that'll clear cache on exit, check out the various forums for GC supporters that have sprung up.