Mozilla 2/2008Q2 Goals: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎ActionMonkey: ActionMonkey: Preserve link for JS_THREADSAFE task)
Line 8: Line 8:
* Implement the automatic-rewriting pass to get rid of null-checks for OOM. NOTE: this doesn't mean we will actually land the patch this quarter; that depends on identifying "large allocations" and exempting them from the normal rules
* Implement the automatic-rewriting pass to get rid of null-checks for OOM. NOTE: this doesn't mean we will actually land the patch this quarter; that depends on identifying "large allocations" and exempting them from the normal rules
* jemalloc+GC API design complete, see [[GC_API]]
* jemalloc+GC API design complete, see [[GC_API]]
* In jemalloc, implement data structures and algorithms needed by the GC ([https://bugzilla.mozilla.org/show_bug.cgi?id=427231 bug 427231]).


== Automatic Rewriting/Analysis ==
== Automatic Rewriting/Analysis ==

Revision as of 14:41, 5 April 2008

These are the Mozilla 2 team goals for Q2 2008:

THIS IS A VERY ROUGH DRAFT.

Memory

  • In jemalloc, implement no-fail OOM by default and a separate can-fail allocator API: see Mozilla 2/Memory
  • Implement the automatic-rewriting pass to get rid of null-checks for OOM. NOTE: this doesn't mean we will actually land the patch this quarter; that depends on identifying "large allocations" and exempting them from the normal rules
  • jemalloc+GC API design complete, see GC_API
  • In jemalloc, implement data structures and algorithms needed by the GC (bug 427231).

Automatic Rewriting/Analysis

  • Finish dehydra and deploy on debug+leak tinderboxes, linux and mac
  • Finish analysis passes needed for XPCOMGC
  • See OOM goal above
  • GCC summit presentation and continuing GCC community involvement
  • Release Dehydra 1.0 and Pork

ActionMonkey

XPCOMGC

  • Browser running mostly-correctly, and gather performance/memory statistics