c-icap exiting on signal 10 and 11

[Marko Cupać]

Hi,

I have squid + squidclamav setup for ~1000 users on FreeBSD 9.2-RELEASE
x64 server with 2Gb of RAM. Both c-icap and squidclamav are at their
default settings.

I am getting frequent errors:
Feb 26 10:39:14 rsbgyucnix04 kernel: pid 1537 (c-icap), uid 959: exited
on signal 10
Feb 26 10:39:14 rsbgyucnix04 kernel: pid 1552 (c-icap), uid 959: exited
on signal 10
Feb 26 10:39:22 rsbgyucnix04 kernel: pid 1553 (c-icap), uid 959: exited
on signal 11
Feb 26 10:39:22 rsbgyucnix04 kernel: pid 5099 (c-icap), uid 959: exited
on signal 11
Feb 26 10:40:07 rsbgyucnix04 kernel: pid 5351 (c-icap), uid 959: exited
on signal 10
Feb 26 10:40:07 rsbgyucnix04 kernel: pid 7067 (c-icap), uid 959: exited
on signal 10

This happens on both bare metal server (old HP Proliant DL350G4) and
virtual server running in VMware ESXi. I tested bare metal with
Memtest86+, no signs of RAM problems.

Should I tweak c-icap settings (e.g. MaxServers or
MaxRequestsPerChild)? Or could this be software bug?

Thank you in advance,
-- 
Marko Cupać