I'm seeing this too; I'm attaching the /var/log/squid-deb-proxy/cache.log, which seems to indicate that squid is attempting to allocate approximately 10PB of memory for swap. This, obviously, fails; hence the abort.
I think this might have to do with corrupted files in /var/cache/squid-deb-proxy; after blowing away that directory, squid-deb-proxy will successfully start. Until it fails again - maybe the problem is unclean shutdown?
I'm seeing this too; I'm attaching the /var/log/ squid-deb- proxy/cache. log, which seems to indicate that squid is attempting to allocate approximately 10PB of memory for swap. This, obviously, fails; hence the abort.
I think this might have to do with corrupted files in /var/cache/ squid-deb- proxy; after blowing away that directory, squid-deb-proxy will successfully start. Until it fails again - maybe the problem is unclean shutdown?