I'm looking into memory leak issues with mod_skinny, and it seems clear that it's repeatedly allocating memory when it doesn't really need to hang onto it permanently. Since it has both a long standing connection to each device (listener) and has requests coming in regularly that currently are allocating memory and appear to be leaking it since the listener stays around. Would having the code allocate a new temporary sub-pool for each request that comes in be appropriate, or would it be better to just use regular malloc for those allocate/use/destroy cases? -- Nathan ------------------------------------------------------------ Nathan Neulinger nneul@mst.edu Missouri S&T Information Technology (573) 612-1412 System Administrator - Architect