Closed Bug 751227 Opened 10 years ago Closed 10 years ago

Remove nsPresShell::mStackArena, make it a separate stack class


(Core :: Layout, defect)

Not set





(Reporter: MatsPalmgren_bugz, Assigned: MatsPalmgren_bugz)


(Whiteboard: [MemShrink])


(1 file, 1 obsolete file)

nsPresShell::mStackArena takes up a lot of space permanently even though
it's only used as temporary storage in a couple of XUL layout methods.

Before this patch, sizeof(nsPresShell) is 552 making jemalloc allocate
a 1024 byte block for it.  Additionally, mStackArena is a 4096 block
even when it's not actually used.  (This is on 64-bit Linux)

With the patch, sizeof(nsPresShell) is 512, fitting exactly into a 512
jemalloc chunk.  mStackArena is removed, so the total saving is 4.6kB.
Attached patch fix (obsolete) — Splinter Review
The StackArena/StackBlock/StackMark code is verbatim copies, except that
I made StackArena completely private and AutoStackArena a friend to forbid
any direct use of StackArena.
Attachment #620361 - Flags: review?(roc)
I'm not sure the two places where this code is used really justifies its
existence.  The only benefit I see is that it coalesces the alloc/free
of (presumably) many small objects, and it avoids the realloc copying in
nsTArray f.e. should we use that instead.  Do we have some collection type
that use "roped" multiple buffers internally to avoid copying?
> in a couple of XUL layout methods

One XUL and one Table layout method, actually.
Try results pending, together with bug 750745 patches:
Whiteboard: [MemShrink]
> Before this patch, sizeof(nsPresShell) is 552 ... (This is on 64-bit Linux)

Uhm, a Linux64 debug build to be exact, so the clown shoes on nsPresShell
is likely less of a problem in release builds, I'll check what the real
numbers are.  The 4096 bytes mStackArena size should be accurate though --
those structs does not have DEBUG-only members.
FYI, I found bug 486066 with discussion about removing the StackArena class.
Comment on attachment 620361 [details] [diff] [review]

Review of attachment 620361 [details] [diff] [review]:

Looks good!

::: layout/base/StackArena.h
@@ +87,5 @@
> +    return mStackArena->Allocate(aSize);
> +  }
> +
> +private:
> +  static StackArena* mStackArena;


::: layout/tables/SpanningCellSorter.h
@@ +76,5 @@
>       */
>      Item* GetNext(PRInt32 *aColSpan);
>  private:
>      nsIPresShell *mPresShell;
> +    mozilla::AutoStackArena mArena;

Putting this in the class is a bit dangerous because it permits non-stack behavior. How about moving it to a local variable in some function?
Doesn't NS_STACK_CLASS on SpanningCellSorter take care of that?
AutoStackArena should probably have NS_STACK_CLASS too, but I wasn't sure if all
compilers would grok that.
I think I'd rather have NS_STACK_CLASS on AutoStackArena and put it explicitly in a method's stack frame.
Attached patch fix, v2Splinter Review
Nits fixed.
Attachment #620361 - Attachment is obsolete: true
Attachment #620361 - Flags: review?(roc)
Attachment #620762 - Flags: review?(roc)
The size of nsPresShell in an Opt build on Linux64:
  before: sizeof=496 moz_malloc_size_of=504
  after:  sizeof=456 moz_malloc_size_of=456
so the total saving is (with the 4096 of mStackArena) 4144 bytes.

After shuffling fields around, and narrowing the size of some, I get:
  sizeof=408 moz_malloc_size_of=408
I'll file a separate bug for that.
Comment on attachment 620762 [details] [diff] [review]
fix, v2

Review of attachment 620762 [details] [diff] [review]:

::: layout/tables/BasicTableLayoutStrategy.cpp
@@ +264,5 @@
>  {
>      nsTableFrame *tableFrame = mTableFrame;
>      nsTableCellMap *cellMap = tableFrame->GetCellMap();
> +    mozilla::AutoStackArena mArena;

Just call this "arena" since it's not a member.
Attachment #620762 - Flags: review?(roc) → review+
> Just call this "arena" since it's not a member.

Thanks, fixed.
Target Milestone: --- → mozilla15
Closed: 10 years ago
Resolution: --- → FIXED
How many nsPresShells do we have live at a time?
One per document being rendered.
It seems we keep a few in the bfcache as well.  Here's the results I get:
start up with 1 tab (about:home)
  3 shells
load in that tab --, about:home, ...
 +1 for each page up to 6
create a new tab (about:home):
 +1 (total 7)
loading in tab 2 --, about:home, ...
 +1 for each page up to 10
Oh, right.  One per document being shown or in bfcache.  ;)
Yeah, and not to forget, each window has a XUL document.

I was quite impressed to see that "Minimize memory usage" in about:memory
reclaims the ones in bfcache.
You need to log in before you can comment on or make changes to this bug.