I can also confirm this exact problem occurring in 12.04 32-Bit, in a server configuration with dnsmasq. Squid is configured to use 127.0.0.1 (dnsmasq) as a name server. dnsmasq is configured with a set of upstream DNS servers.
dmesg:
[ 17.256295] init: squid3 main process (1236) killed by ABRT signal
I can also confirm this exact problem occurring in 12.04 32-Bit, in a server configuration with dnsmasq. Squid is configured to use 127.0.0.1 (dnsmasq) as a name server. dnsmasq is configured with a set of upstream DNS servers.
dmesg:
[ 17.256295] init: squid3 main process (1236) killed by ABRT signal
/var/log/ squid3/ cache.log:
2012/04/30 00:04:26| HTCP Disabled.
2012/04/30 00:04:26.443| WCCPv1 disabled.
2012/04/30 00:04:26.443| WCCPv2 Disabled.
2012/04/30 00:04:26.443| Squid plugin modules loaded: 0
2012/04/30 00:04:26.443| Adaptation support is off.
2012/04/30 00:04:26.443| Ready to serve requests.
2012/04/30 00:04:26.443| Store rebuilding is 11.49% complete
2012/04/30 00:04:26.443| Reconfiguring Squid Cache (version 3.1.19)...
2012/04/30 00:04:26.443| FD 14 Closing HTTP connection
2012/04/30 00:04:26.443| assertion failed: disk.cc:377: "fd >= 0"
I'm starting squid from /etc/rc.local as a workaround.