squatter exits with "fatal error: Virtual memory exhausted" on huge mailbox

[Sebastian Hagedorn]

--On 13. Juli 2009 14:53:31 +0200 Pascal Gienger 
<Pascal.Gienger at uni-konstanz.de> wrote:

> Sebastian Hagedorn schrieb:
>>>> fatal error: Virtual memory exhausted
>
>> Of course it's possible that it then tried to allocate one huge chunk,
>> but I can't see that. Are there better tools to monitor the memory
>> allocation of a process?
>
> Swap file/partition full?

Unlikely.

> Background:
> I think the message "Virtual memory exhausted" is coming from your
> operating system and not from the squatter process.

I disagree.

> Squatter would have been said
>
>    switch (err) {
>    case SQUAT_ERR_OUT_OF_MEMORY:
>      fprintf(stderr, "SQUAT: Out of memory (%s)\n", s);
>      break;

But:

lib/xmalloc.c:    fatal("Virtual memory exhausted", EC_TEMPFAIL);

This code actually can't be reached:

      b->buf = (char*)xrealloc(b->buf, len);
      if (b->buf == NULL) {
        squat_set_last_error(SQUAT_ERR_OUT_OF_MEMORY);
        return NULL;
      }

If the xrealloc fails, the "fatal" above is called within that routine.
-- 
     .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:.
                 .:.Regionales Rechenzentrum (RRZK).:.
.:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20090713/f59936cc/attachment.bin