Question about Cache Size

[james]

james wrote:
> Hey everyone,
>
> In trying to diagnose why the varnish child dies at seemingly random 
> times, I started varnish with -d -d and waited for a crash. This is what 
> I got in the output:
>
> Child said (2, 16094): <<Assert error in STV_alloc(), stevedore.c line 70:
>   Condition((st) != NULL) not true.
>   errno = 107 (Transport endpoint is not connected)
>  >>
> Cache child died pid=16094 status=0x6
> Clean child
> Child cleaned
> start child pid 18886
> Child said (2, 18886): <<Child starts
> managed to mmap 565284864 bytes of 565284864
> Ready
> CLI ready
>  >>
>   

This issue is not effecting me anymore after moving to a 64bit system.

Alas, I am experiencing another issue using varnish-1.2. After purging 
from the cache (using url.purge *.css), the child will die and the 
management process goes to 100% cpu. From running in debug mode:

storage_file: filename: /var/cache/varnishd//varnish.BIT37f (unlinked) 
size 10240 MegaBytes.
Using old SHMFILE
rolling(1)...
rolling(2)...
start
start child pid 20178
200 0      

Child said (2, 20178): <<Child starts
managed to mmap 10737418240 bytes of 10737418240
Ready
CLI ready
 >>
Cache child died pid=20178 status=0xb
Clean child
Child cleaned
start child pid 20199
Child said (2, 20199): <<Child starts
managed to mmap 10737418240 bytes of 10737418240
Ready
CLI ready
 >>

Is there anything else I should to to help track down the issue? Is it 
advisable to go to 1.1.2?

-- james