I didn’t knew it existed until recently, that I saw all my memory was eaten up and suddenly I was using my SWAP instead of my memory, and it was fully loaded.

What’s my surprise? I have 2G in memory and 1113M of it was cache, and 1G of swap full as well. The worst thing is that I reboot my machine and without starting anything I get 903M of cache full, out of nowhere!

I start to track what’s the issue, where’s the leak, and found that if I killed tracker-store early then my memory stopped being loaded of cache.

There’s a bug, already reported, it’s #612242 and the workaround given is to nuke the database with tracker-control -r.

It worked. Now my cache is not full, but since I just did it I don’t know if in some days my tracker-cache will be full again and eating all my memory.

Just wanted people know there was a work-around at least and you could use your computer again.

I was searching through the internet what was I doing wrong, I wrote to the polipo-user list but my email got stuck on moderation, and my connection is really shitty (that’s why I’m using polipo the way I’m using it). I have relaxTransparency and mindlesslyCacheVary set to true, but I don’t need so aggresive caching in my development stages that are located under *.local and another development subdomain on the net.

Already tried setting uncachableFile to /etc/polipo/uncachable and to ~/.polipo-uncachable, according to the web-config thing is properly setted up, but can’t get it to recognize it’s content. I first thought it was I was writing bad the regex, .*\.local but it does work in the /etc/polipo/forbidden file. Besides, adding complete domains to the uncachable file doesn’t works neither. Could someone confirm this or throw me a hand on this? I’m using 1.0.4.1-1.1 version which is the last one on unstable repos.