!/bin/upas/marshal -s 'Re: [9fans] aux/acidleak pool pathology' -R /mail/fs/mbox/272 [email protected] > >> if upas/fs is allocating arbitrarily large buffers, > >> then its allocation behavior is broken too. > > > > there are a fixed number of large buffers. up to 15 messages > > and mdir uses dirreadall so it can qsort. the qsort is easy enough > > to eliminate, but it's more difficult to bound message buffers. > > i never said fixing it was easy. ;-)
from the embarrassing bugs department.... going to all that trouble might not be worth it at ~10000 message mailboxes. it turns out that a bug i introduced earlier in the week in imap4d was causing all mailboxes to remain open. so the 400mb process had grown from a 50mb process due to a few esoteric leaks and having 1.5gb in 203 mailboxes open all at once. it's suprising that upas/fs did as well as it did. combining the tricks from the week shrinks this process to a slightly more manageable 12mb. unfortunately, i think this will just encourage users to aim for 100000 messages in their inbox. ☺ - erik
