Description:
------------
setup:

php-fcgi 5.2.6 (not 5.2.5 as above, need to add that as an
option ;-)
lighttpd 1.4.19
apc-CVS-2008-11-26

apc compiled with mmap memory, IPC semaphore locking.

enough php code to fill the cache
apc.shm_size=30 (make it small enough so that the code for
one request cannot fit, yes we do have 30MB of code in one
request)
apc.ttl=10 (any value >0)

php-fcgi segfaults on every request which "overfills" the
cache. the cache full count after such a request proces the
overfill.

APC-3.0.19 does not segfault under the same conditions.

A similar problem occurs when apc.ttl=0 (ie complete clean
on cache_full) but in this case you must hit the cache with
some concurrency (we are running on an 8cpu-core machine so
the concurrency is quite real). siege of 15 concurrent users
is sufficient to produce the segfault after a few seconds in
our setup.

We realise that these are extreme conditions (ie we have a
cache size which is really too small for the code), however
on our production machines which have enough cache 99% of
time, but do require cache_expunge occasionally (once per
week perhaps) we also get the same problem. We have reduced
the problem to something we can reproduce reliably in a
short period of time by making the conditions extreme.





Reproduce code:
---------------
hit once to overfill cache and observe segfault

Expected result:
----------------
no segfault

Actual result:
--------------
segfault