Chris Waterson wrote:
> - nsSocketTransport accounts for almost 5% of the memory. I would've
> thought any large buffers allocated during the load would go away after
> we'd finished loading the page!
The memory you're seeing consumed here is by nsSocketTransport objects,
which does not include the 8k buffer that each one creates. It strikes
me as odd that we're caching this many transports (http should be
sparking each of them) (http says it only caches 8),
http is supposed to be "caching" (for reuse) only 8 socket transports
(so says the #define default as well as the default pref value). When
http goes to clean them up I see an outstanding ref of 1 on the
transports (so either http is dropping a ref somewhere, or someone
further up the chain is hanging onto the http channel (which holds a ref
to the socket trans).
the socket transport will never create more than 50 sockets, though you
can certainly create more sockettransports (the requests will queue up).
Jud
