You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.




status update

maintained by Tim Rowley <tor@cs.brown.edu>

Last Updated Wednesday January 3, 2001

This status update page is updated every week. To get updates and news throughout the week you are invited to check out mozillaZine, a site devoted to Mozilla advocacy.

Previous Updates


Friends of the Tree

  • Brian Ryner and John Myers for excellect tree cleaning work. They both killed a ton of unused code. - Dan Mosedale
  • David Baron for profiling and code cruft removal. - Stephen Donner

Missing Status Reports

The following engineering groups failed to submit a status report by the Wednesday 6:00pm EST deadline.
  • Composer
  • MailNews
  • Navigator
  • Necko/Imglib
  • Rendering
  • XML/DOM
  • XPToolkit
Module Updates
GTK Plugins
December 29
Submitted by Christopher Blizzard <blizzard@redhat.com>

GTK based plugins should handle focus properly now. This means that if you want to want to write a plugin you can do it in a toolkit.

http://bugzilla.mozilla.org/show_bug.cgi?id=61782

Footprint
January 2
Submitted by Chris Waterson <waterson@netscape.com>
Here are minutes from the 12/20 footprint meeting (better late than never). Please look through this to remind yourself what you were supposed to do and reply to this message with a quick status update. Then everyone can be up-to-speed and we can just go through questions and problems. (Tip o' the hat to buster for the pointy-haired meeting management suggestion.)
  1. Ongoing memory tracking (curt)
    • Builds were stable (as of 12/20) and we were expecting to see some regular reports posted. Looks like things may have degenerated recently?
    • Still problems with combo boxes crashing embed build. Couldn't find a bug filed on this, although I'm pretty sure there is one. (rods?)
    • winEmbed crashing with `embed' builds?
  2. Code coverage
    • evaughan did detailed analysis
    • discovered amount of unused code in layout DLL == sum of unused code in all other DLLs. jst is doing some DOM refactoring; should re- measure after his work lands.
  3. Style system
    • attinasi's style context sharing has been checked in.
    • attinasi/pierre/evaughan discussing doing sharing at finer granularity, sharing CSS declarations, selectors. pierre has been collecting statistics that point towards this. (pierre, maybe you could share your info with the group
  4. Trace malloc porting
    • mjudge still working on it
  5. Allocation analysis
    • brendan/waterson discover race condition bug that was causing bad data to show up. Still can attribute only 20-25% of growth to live objects.
    • jar/thesteve to investigate fragmentation.
    • kandrot to instrument sbrk() and mmap().
    • buster to look at frame manager structures
  6. Compilers
    • cls to determine if compiling mozilla with gcc-2.95.2 requires libc upgrade to use resulting binary.
    • cls determined that -O2 and -O3 do not make significant difference with respect to overall DLL size.
    • pavlov to investigate new gcc code-gen rumors
    • chofmann to bug waldemar about commercial compilers we could try
  7. Parser
    • harishd decides parser nodes cannot be removed. Will change to arena allocation of nodes and fix leaks.
  8. Leaks
    • thesteve to begin using `--enable-boehm' build to track down leaks.
  9. Project Fu
    • waterson to set up space on gila/website for coordination.
OS/2
January 3
Submitted by Michael Kaply <mkaply@us.ibm.com>

Our two main areas of focus of late have been internationalization (particularly DBCS) and printing. We have made some big strides with both.

We are looking at putting together a Mozilla 0.6 very soon that will contain PSM/NSS.

Bidi
January 3
Submitted by Michael Kaply <mkaply@us.ibm.com>
Bidi is currently in the process of being reviewed. See bug 62777.

Previous Updates