Archive: clearing a Chrome cache on Ubuntu

This 2012 note records a cache-cleaning approach I used while troubleshooting Chrome on an Ubuntu machine accessed remotely. It is not current browser support guidance. Chrome profiles, cache locations, and supported ways to clear browsing data have changed over time.

The issue I was investigating

The browser's desktop search was not returning results, and the remote view made the interface difficult to work with. I also suspected accumulated cached files could be contributing to slow or inconsistent browser behaviour.

Browser caches hold local copies of resources so a later visit does not need to retrieve every file again. Clearing a cache can be useful while diagnosing a stale asset or corrupted local state. It also removes stored browser data, so it should be a deliberate troubleshooting step rather than routine maintenance.

The historical command

The cache path I recorded for that Ubuntu installation was:

ls --all /home/.cache/google-chrome

I then recorded these removal commands:

sudo rm --recursive /home/.cache/google-chrome/
# or
sudo rm --recursive ~/.cache/google-chrome/

Do not run a recursive removal command from this archive without confirming the expanded path and the current Chrome profile location. Administrative access does not make an unverified path safe.

For a current browser issue, start with Chrome's supported "Clear browsing data" controls and the current Ubuntu documentation. Use a profile backup and a narrow, verified path before removing files from the command line.