Platform/2010-11-30

From MozillaWiki

« previous week | index | next week »

Notices / Schedule

Firefox 3.6.13 and 3.5.16

• Created build #2 today, with a fix for bug 614565
• Still plan to release on December 9th

Blocker Report

Firefox 4 Beta

Blocker report for Firefox 4.0.beta8 (as of 2010-11-30 11:03:00.963342-08:00)

Overview
----------------------------------------------

4.0.beta8
      blocking: 188
         fixed: 164
          open:  24

Open Blocker Assignees
----------------------------------------------

   Philipp von Weitershausen [:philikon]:   6 ++++++
                  Blake Kaplan (:mrbkap):   2 ++
              Michael Morgan [:morgamic]:   2 ++
                        Andreas Gal :gal:   2 ++
    Nobody; OK to take it and work on it:   2 ++
          Josh Aas (Mozilla Corporation):   1 +
              english-us@evangelism.bugs:   1 +
                      Axel Hecht [:Pike]:   1 +
                         Jason Orendorff:   1 +
                  Chris Leary [:cdleary]:   1 +
                  Ehsan Akhgari [:ehsan]:   1 +
                        Myk Melez [:myk]:   1 +
                   Jason Duell (:jduell):   1 +
                         general@js.bugs:   1 +
                 Wesley Johnston (:wesj):   1 +

Firefox Development

(from our goals):

Firefox

• [AT RISK] Finish Firefox 4
  • 224 Firefox/Toolkit blockers

• [ON TRACK] API-Complete Jetpack
  • Joint with Jetpack team
  • Currently working towards feature-complete beta SDK

• [ON TRACK] Stand up basic Firefox with Electrolysis
  • Joint with Platform
  • UI may not be functional, should launch and open a web page.
  • Project tracking page

Developer Tools

• [NEW] Finish Firefox 4 developer tools
  • 26 blocking developer tools bugs

• [NEW] Ensure that Firefox 4 ships with a compatible version of Firebug

• [NEW] Publish a roadmap for integrated developer tools in Firefox, including console, inspection, and js debugging

• [NEW] Develop long term plan for Skywriter maintenance/support

Platform

(there is a team-by-team goals breakdown, as well)

• [DONE] Javascript performance near or even with Chrome 5 on their benchmarks (within 20% on SS, 30% on V8), with substantial wins on our benchmarks. (Windows, in-browser.)
• [DONE] Hardware acceleration of video and other HTML and SVG content, as well as user interface, on by default for compatible hardware on all Tier-1 desktop and mobile platforms.
• [DONE] Fully support the WebGL 1.0 spec, with support turned on by default in a Firefox 4 beta on platforms that support OpenGL or OpenGL ES.
• [MISSED] security: zero reproducible high/crit > 30 days
• [DONE] Support multi-process Fennec.
• [DONE] Support Jetpacks running in separate processes and never blocking the Fennec UI. NOTE: jetpack team hasn’t actually integrated this code yet, but it works in small test environments.

GFX

• 123 betaN, final, and Fennec blockers
• OpenGL composited layers on Fennec update (jrmuizel)
  • Sort of usable now, patches need to be finished before they can land though.
  • Performance work still to be done.

Layout

• Blocker count slowly dropping, now 108
  • Many bug fixes in hand
• Lots of editor/contenteditable fixes have landed (ehsan)
  • Google Docs features that were disabled for Firefox (spreadsheet formula syntax highlighting) will be enabled for Firefox 4

Tree Management

Roundtable

• Infallible malloc (added to agenda by Jesse)
  • The problem, which has only recently come to light:
    • We haven’t actually made malloc infallible yet. We already made new infallible for Firefox 4, but many data structures (including arrays and strings) can still misbehave on OOM because malloc can still return NULL.
    • Many exploitable OOM bugs are in system libraries rather than Firefox itself. Replacing malloc may be the only way for us to work around all of these bugs.
    • Security researchers have been reporting many OOM bugs lately.
      • We often can’t reproduce what they see because we OOM slightly earlier or later.
      • This is a recipe for embarrassment when “old” testcases find “new” bugs, as Alex Miller discovered.
  • The plan of record:
    • Fix nsTArray
  • Proposal:
    • Make malloc infallible
    • Fix too-large-allocation crashes (distinct from OOM), which will be obvious in crash-stats.
      • Will require exposing a fallible malloc somehow
      • May require adding methods or variants to string classes, for example.
  • We must run GC and purge caches before giving up or we will have false positive OOMs when tons of memory is not actually live.
    • Need to monitor OS memory pressure and avoid getting close to these false OOMs.
    • This was part of E10s, is it ready for Firefox 4?
  • Damon will organize a smaller meeting later today to discuss this. Email him if you want to be part of that meeting.
• Crash Update
  • Crashes on trunk down considerably – ~5/100 active users.
  • In pretty good shape for Beta8
  • Any stability risks in remaining beta8 blockers we should be aware of?
• Don’t forget to file bugs when you see problems in nightlies.