Hi Chris:
I don't think I understand how these numbers are derived. I find it hard to
believe there are 16 pres shells in memory at any one time for the browser, let
alone 198. My simple testing with viewer on windows shows no pres shell leaks, and
a high water mark for concurrent pres shells at 3 for CNN when CNN pops up a new
browser window prompting me for preference info in addition to the main cnn browser
window. When I load CNN subsequent times, and in fact when I walk a dozen or so of
the top 100, I usually see just 1 pres shell. I think the only exceptions are for
frameset documents. Furthermore, pres shells are only allocated at the expected
times, when a document is being displayed. I don't see any place where we're
allocating pres shells in an unexpected manner.
Regardless, I'm looking into the size of the pres shell. But help me out here, how
come you are seeing so many of them?
Since each URL load creates a new pres shell, and most documents require only a
single pres shell, we might benefit from some technique that reuses the same pres
shell for the base URL display. Something like a pres shell recycler, where the
recycler only holds a single pres shell instance. I'll look into that.
Chris Waterson wrote:
> ---- Base ---- ---- Incr ---- ----- Difference ----
> Type Count Bytes Count Bytes Count Bytes %Total
> TOTAL 40241 1940945 73545 5315142 33304 3374197 100.00
> PresShell 16 51088 198 340706 182 289618 8.58
>
