On Sun, Nov 16, 2014 at 09:49:06PM +0000, cj wrote: > In article <20141116145722.gc21...@platypus.pepperfish.net>, > Rob Kendrick <r...@netsurf-browser.org> wrote: > > Currently, if NetSurf crashes (or your computer does) without > > quitting cleanly, newly-created cached items will be "leaked"; ie > > they will not be stored in the index which is written out on exit. > > Ahhh - that could explain it. My machines normally run 24/7, and the > only time Netsurf is quit is when I move to the most recent version, > which may be a week or more between upgrades. I do get the occasional > crash of Netsurf, so it could be that a week or more of cache > contents is not being indexed.
This does sound like it may be the cause then. A solution (ie, detection of an unclean exit and thus a garbage collection and index rebuild etc) is on the to do list. Sadly I think the only solution at the moment however is to empty the whole cache directory manually. B.
