103713 - Footprint

Status: RESOLVED FIXED

(Core Graveyard :: Tracking, defect, P3)

Description

[Nobody; OK to take it and work on it]

* Please do not change the dependencies for this bug. 
* Please do not begin a discussion in this bug, but in a newsgroup or by mail. 
* If you add yourself to the CC list, please do not add a comment.

This is part of a set of bugs being used to track and consider mozilla.org's
goals for Mozilla 1.0. However, if a bug is part of this dependency tree, that
does not necessarily mean it will be fixed by the release of Mozilla 1.0. If you
think a bug fits with these goals, and you would like to nominate it for Mozilla
1.0, please add the mozilla1.0 keyword to that bug. Please do not change the
dependencies for this bug.

Comment 1

[Nobody; OK to take it and work on it]

"Footprint" includes:

Code footprint
  - Remove deadwood (e.g., viewmanager2) 

Data footprint
  - being in a steady state, excluding leaks, given a string of URLs
  - plugging leaks

Comment 2

[Brendan Eich [:brendan]]

My notes were unclear, or got garbled -- the point about steady state is not
that we don't leak -- that's item 2 under data footprint.  The point is that,
ignoring or fixing leaks, our data footprint is small enough for a useful range
of target hardware (e.g., devices with 32MB RAM and virtual memory).  We need to
refine the target range description, but I wanted to clarify the issue here ASAP.

I think these bugs need owners, so I'm taking this one.  Anyone want to help?

/be

Comment 3

[Brendan Eich [:brendan]]

After the bug tree listed in the 1.0 manifesto got slashdotted, it rusted as
drivers kept their own lists for each milestone, and delegated performance and
footprint tracking to [e-mail], who did an excellent job.

/be