Meeting Notes Meetings notes from the Mozilla community

Notices/Schedule (sylvestre/lmandel)

Next Merge: May 11, 2015		Next Release: May 12, 2015
Trains
Central: 40	Aurora: 39	Beta: 38	Release: 37

Only two weeks until the next Firefox release date! (2015-05-11)

Layout (David Baron)

Off-main-thread animations now enabled on all platforms for Nightly and Aurora (bug 980770). This means many animations of the transform and opacity properties will now run on the compositor thread, with fewer updates on the main thread.

Media

We shipped some MSE fixes in the Firefox 37.0.2 chemspill, so YouTube will re-enable HTML5 video for Firefox 37.0.2 on Windows next week.

Performance (Vladan Djeric)

Aaron Klotz and Ben Turner paid a visit to Adobe’s Flash team at their SF offices. They were able to provide fixes for several Flash player issues! An example of their work is in bug 1133351. This particular patch also landed in our codebase.

Many Telemetry histograms automatically expired in Nightly 40. Check Histograms.json and bug 1156565 to see if your histogram needs to be updated.

Telemetry unification work is continuing, Phase 3 is tracked in bug 1120356. Enabling unified Telemetry (i.e. FHR + Telemetry) might get pushed back to Firefox 40.

Among the latest Telemetry changes, Telemetry will submit data more aggressively to make analyses more reliable (akin to FHR) and to reduce reporting latency. Additionally, unified Telemetry now archives Telemetry data on the client for 6 months — this archive will be used to power the Firefox Self-Support feature.

Yoric added a “Task Manager” feature to Nightly 40 (bug 674779) to identify tabs and add-ons that are consuming the main thread’s time and slowing down Firefox. Specifically, it reports the time spent by the main thread inside different JS compartments. You can see a very rough UI for this feature by opening about:performance in Nightly. For overhead reasons, the feature currently does not measure time spent in compartments belonging to Firefox’s own chrome JS code.

The Performance team, alongside Platform teams, will be studying page scrolling & page navigation performance on desktop & Android in Q2: https://wiki.mozilla.org/Firefox/Content_Performance_Program

The Places database work done by the “Forget” toolbar button, the “Forget Site” history-menu feature, and the “Clear recent history” feature has been moved off the main thread (bug 1076775). Less jank!

If you notice any plugin issues (crashes, videos not loading, etc), please file a bug and mark it as blocking the async plugin initialization feature (bug 1116806).

Notices/Schedule (sylvestre/lmandel)

Next Merge: May 11, 2015		Next Release: May 12, 2015
Trains
Central: 40	Aurora: 39	Beta: 38	Release: 37

Only two weeks until the next Firefox release date! (2015-05-11)

Layout (David Baron)

Off-main-thread animations now enabled on all platforms for Nightly and Aurora (bug 980770). This means many animations of the transform and opacity properties will now run on the compositor thread, with fewer updates on the main thread.

Media

We shipped some MSE fixes in the Firefox 37.0.2 chemspill, so YouTube will re-enable HTML5 video for Firefox 37.0.2 on Windows next week.

Performance (Vladan Djeric)

Aaron Klotz and Ben Turner paid a visit to Adobe’s Flash team at their SF offices. They were able to provide fixes for several Flash player issues! An example of their work is in bug 1133351. This particular patch also landed in our codebase.

Many Telemetry histograms automatically expired in Nightly 40. Check Histograms.json and bug 1156565 to see if your histogram needs to be updated.

Telemetry unification work is continuing, Phase 3 is tracked in bug 1120356. Enabling unified Telemetry (i.e. FHR + Telemetry) might get pushed back to Firefox 40.

Among the latest Telemetry changes, Telemetry will submit data more aggressively to make analyses more reliable (akin to FHR) and to reduce reporting latency. Additionally, unified Telemetry now archives Telemetry data on the client for 6 months — this archive will be used to power the Firefox Self-Support feature.

Yoric added a “Task Manager” feature to Nightly 40 (bug 674779) to identify tabs and add-ons that are consuming the main thread’s time and slowing down Firefox. Specifically, it reports the time spent by the main thread inside different JS compartments. You can see a very rough UI for this feature by opening about:performance in Nightly. For overhead reasons, the feature currently does not measure time spent in compartments belonging to Firefox’s own chrome JS code.

The Performance team, alongside Platform teams, will be studying page scrolling & page navigation performance on desktop & Android in Q2: https://wiki.mozilla.org/Firefox/Content_Performance_Program

The Places database work done by the “Forget” toolbar button, the “Forget Site” history-menu feature, and the “Clear recent history” feature has been moved off the main thread (bug 1076775). Less jank!

If you notice any plugin issues (crashes, videos not loading, etc), please file a bug and mark it as blocking the async plugin initialization feature (bug 1116806).

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (lsblakk/sylvestre/lmandel)

Next Merge: May 11, 2015		Next Release: May 12, 2015
Trains
Central: 40	Aurora: 39	Beta: 38	Release: 37

• We shipped a Firefox 37.0.1 desktop and mobile chemspills last week.
• Firefox 38 Beta 1 shipped last week.
• Updates have been re-enabled for Aurora.
• 5 weeks until the next merge date (2015-05-11).

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

Tree Closing Window on Saturday April 18, time TBD.

• tracking bug 1151645
• at least 4-5 hours of work.

MemShrink (njn)

Brian Hackett took advantage of the removal of object parents to reduce the size of base shapes (bug 1143256). The JS engine creates many of these to track the characteristics of JS objects.

Nick Fitzgerald greatly reduced the amount of memory used for saving JS exception stacks (bug 1038238). This reduced the memory of a test case compiled from Dart to JS from over 1GB to around 170MB (bug 1125259). Blog post: http://fitzgeraldnick.com/weblog/61/

Seth Fowler fixed a bad leak regression (bug 1150127) where closing a page while it was in the process of loading could leak the page and cause long browser pauses. Seth also fixed a pair of issues that caused very large memory usage (more than 1GB) when scrolling in the downloads list (bug 1148682 and bug 1148684).

Bill McCloskey fixed an issue where a docshell was being held alive for too long on e10s (bug 1137933). This was one of the remaining blockers to enabling e10s Mochitest browser-chrome tests, which will give us more test coverage for leaks.

Media

We shipped MSE (Media Source Extensions) for YouTube in Firefox 37 on Windows Vista+. Unfortunately, we discovered multiple unrelated issues in the release channel that all manifest themselves as “video is black”:

bug 1151721: Intel GPU driver bug (will be hotfixed by bug 1152630)
bug 1151638: NoScript blocking MSE JS (will be fixed soon in NoScript 2.6.9.21)
bug 1135078: IPv6 problems (partially fixed bug 1135078)

YouTube helped us quickly revert all Firefox users from HTML5 video to Flash. Once the problems were identified, YouTube was able to switch OS X and Windows Vista+ pre-channels back to HTML5 video. We plan to ship MSE for YouTube on Windows Vista+ in Firefox 38 (or 37 if hotfix bug 1152630 is released soon) and on OS X in Firefox 38 (or possibly slip to 39).

Need To Know

Notices/Schedule (lsblakk/sylvestre/lmandel)

Next Merge: March 30, 2015		Next Release: March 31, 2015
Trains
Central: 39	Aurora: 38	Beta: 37	Release: 36

Only two weeks and two beta builds until Firefox Beta 37 is released. The new “Tracking Firefox” dashboard shows tracked bugs for the Aurora and Beta releases.

Quality Programs

(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

OrangeFactor (ryanvm)

RyanVM sends a major shout out to ttaubert for being on an orange fixing tear last week.

MemShrink (njn)

Mike Hommey enabled jemalloc3 (bug 762449) on Nightly. It’s configured to *not* ride the trains for now. There are a number of perf regressions and some crashes that Mike is diligently working through.

Team Stand-ups

Media (mreavy)

The media team is close to shipping Media Source Extensions (MSE bug 1083588) for YouTube. MSE improves HTML5 video performance as YouTube transitions its default video player from Flash to HTML5 video. The team plans to ship MSE on Windows in Firefox 37, OS X in Firefox 38, and then Linux. Be on the look out for any YouTube bugs, such as videos that won’t load or get stuck rebuffering.

Performance (vladan)

Telemetry and FHR measurements were unified into a single system on Nightly 39 (bug 1069869). The old FHR will still be around for a couple of releases. The unified Telemetry client-side is still being “stabilized”, so Telemetry from Nightly 39 isn’t reliable yet. Be very careful when interpreting Nightly 39 data!

The unified Telemetry pings are sent to a new Telemetry backend (DataPipeline) which will support streaming analyses. The Telemetry wiki is now up to date with information about Telemetry client-side & server-side workings: https://wiki.mozilla.org/Telemetry. We added a Telemetry “errata” page to help with analyzing Telemetry data: https://wiki.mozilla.org/Telemetry/Errata.

Many Telemetry histograms will automatically expire in Firefox 40. Check Histograms.json to see if the expiry version of your telemetry probes should updated.

Test results comparing e10s vs non-e10s Talos scores and an explanatory blog post are coming soon. Results in very raw form: http://pastebin.com/raw.php?i=D7fr2EtM

Aaron Klotz created a tool for visualizing Windows attached input queues, as detailed on his blog: http://dblohm7.ca/blog/2015/03/03/attached-input-queues-on-firefox-for-windows. Attached input queues can cause odd problems like bug 1105386 where a page won’t load or render if the mouse is not moving.

With bug 1128768, we can now gather information about the amount of jank caused by different types of Flash content. This will be used to quantify the benefit of targeting Shumway at different types of Flash content.

Per-compartment CPU accounting (bug 674779) should land in the next week or two. Use it to report add-ons that use too much CPU or CPOWs (e.g. bug 1136923).

Shumway (tschneidereit)

The team’s current focus is playing Flash ads in Shumway instead of Flash. Using Shumway will reduce the number of Flash plugin instantiations, which is correlated with Flash deadlocks, and reduce page jank. Flash ads have also exploited Flash security bugs to install malware. Shumway should protect against many of those exploits.

Shumway now plays IMDb trailer videos on Nightly (bug 1137433) and substantial progress is being made on a verifiable sandboxed. An implementation of AS3’s meta-object protocol that should be pretty faithful to Flash’s and a new Shumway interpreter should land soon. This enables proper handling of SecurityDomains, a crucial Flash security feature.

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (sylvestre/lmandel)

Next Merge: April 6, 2015		Next Release: April 7, 2015
Trains
Central: 39	Aurora: 38	Beta: 37	Release: 36

• The next merge date is March 30, just four weeks away. Firefox 37 and 38 releases have been moved up one week to avoid conflicts with holidays.
• Firefox 38 will be the “spring thing” Firefox release and the next ESR, retiring ESR 31.
• Dashboard showing tracked bugs for Beta and Aurora: http://people.mozilla.org/~klahnakoski/platform/releases.html

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

The next Tree Closing Window is scheduled for Saturday, March 14.

MemShrink (njn)

A new Windows-only “address-space” memory reporter (bug 1134030) landed which may help debug Windows graphics and video memory usage. If you have other ideas on how to measure Windows graphics and video memory usage, contact Nicholas Nethercote.

Shumway (tschneidereit)

Shumway made some headlines a couple weeks ago (TechCrunch and CNET) when it was enabled (in the Nightly channel only) for playing Amazon product tour videos. Shumway has now been enabled for playing IMDb trailer videos.

WebAPI (overholt)

Service Workers (bug 1059784) should land soon. (Famous last words.)

IndexedDB performance work will also land soon: bug 866846 will enable SQLite’s WAL journal and bug 1112702 will change transactions to be non-durable. These SQLite options favor performance over durability like Chrome and IE do. They do not increase the risk of database corruption.

Roundtable

(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

• Mozilla’s Firefox OS team is at the MWC 2015 (Mobile World Congress) in Barcelona this week, announcing new Firefox OS partners, markets, and hardware form factors.
• Mozilla is also at GDC 2015 (Game Developer Conference) in San Francisco, where Epic Games and Mozilla announced Unreal Engine 4.7 support for HTML5/WebGL export.

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (lsblakk/sylvestre/lmandel)

Next Merge: February 23, 2015		Next Release: February 24, 2015
Trains
Central: 38	Aurora: 37	Beta: 36	Release: 35

Build Changes (gps)

(Build changes of which engineers should be aware.)

RelEng (catlee)

(Repo, test, and other information for engineers from the release engineering team.)

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

Quality Programs

(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

MemShrink (njn)

<Read Only>

• Memory usage of MSE is unpredictable and a concern.
• The change to PLDHashTable and nsTHashtable mentioned in last week’s meeting (implementing lazy storage) had to be backed out for some intermittent crashes, alas.

Team Stand-ups

(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

Electrolysis (e10s) (blassey)

• Please help test e10s in Nightly!
  • Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect

Roundtable

(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

Links

Mailing List Threads

(Threads that are likely to be of interest to engineering from various mailing lists.)

Good Reads

(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

irc #planning Log From This Meeting

---

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (lmandel)

Next Merge: February 23, 2015		Next Release: February 24, 2015
Trains
Central: 38	Aurora: 37	Beta: 36	Release: 35

• Desktop 36 Beta 7
  • shipped on Saturday – thanks to the teams that helped ship on the weekend
  • disabled MSE
  • did not ship on Windows because we were waiting for a fix for YouTube
  • we will likely ship a Desktop Beta 10 as a result

• Desktop and Mobile Beta 8 should ship today

• Reminder that the next merge is < 2 weeks away. 38 is the next major Firefox release and the next ESR release. Get yer fixes in!

• Aurora 37 is still not in good shape stability wise

• ekyle has created a page that shows Firefox tracked bugs per dev team for Beta and Aurora. This will be going up on the in office screens soon. Check it out. http://people.mozilla.org/~klahnakoski/platform/releases.html

Build Changes (gps)

(Build changes of which engineers should be aware.)

RelEng (catlee)

(Repo, test, and other information for engineers from the release engineering team.)

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

Quality Programs

(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

MemShrink (njn)

<Read Only>

PLDHashTable (and nsTHashtable and friends) now do not allocate any entry storage until the first element has been added. This makes empty tables more space-efficient and there’s no longer any need to lazily initialize such tables.

Stability (kairo)

<Read Only>

• Overall numbers are still bad for everything else than release.
  • With 35.0.1 released, Firefox for Android looks fine on release now.
  • Desktop Beta should improve with MSE disabled in today’s beta. D2D 1.1 will also be disabled before we ship 36. We’ll try again next cycle.
  • Developer Edition sees a real lot of graphics crashes, we’ll need to see that cleaned up, hopefully a big part of that before we go to beta.

Team Stand-ups

(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

Desktop Platform (bsmedberg)

• Reminder: FHR and telemetry are being unified, hopefully for 38 cycle. All new measurements should be added to telemetry, no matter whether you want them for only prerelease or release populations.

Electrolysis (e10s) (blassey)

• Please help test e10s in Nightly!
  • Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect

GFX (milan)

<Read Only>

• Planned “final” push for Lollipop, Silk in progress. More so for Silk than Lollipop, there are things outside our hands for Android L.
• Chasing down those Windows OOMs.
• Still a few unresolved Windows 7 issues on Beta 36.

Media (mreavy)

<Read Only>

1. What has your team done since last week that might impact others?

• OpenH264 v1.3 now being pushed to release-channel users

2. What will your team do this week that might impact others?

• Fixing some OpenH264 vs WebRTC 40 update issues (packetization)
• Working on some regressions for getUserMedia (camera access) on specific Android devices
• Loop/Hello will be updating the server and unthrottling soon
• Preparing to land webrtc renegotiation (windows timer limits, etc)

Performance (vladan)

What has your team done since last week that might impact others?

1. You can now do custom Telemetry analyses using a Spark cluster consisting of multiple nodes! Analyses of large volumes of data should be significantly faster.

• Launch a cluster from https://telemetry-dash.mozilla.org/
• Instructions: http://robertovitillo.com/2015/01/16/next-gen-data-analysis-framework-for-telemetry/
• You will soon be able to use Spark for Telemetry cron-jobs as well

2. FHR & Telemetry are being unified and some of the patches have caused a couple of Telemetry outages on Nightly 38. Make sure to check for expected # of submissions when looking at Telemetry dashboards or doing a custom Telemetry analysis.
3. David Teller (Yoric) has been on sick leave for the last few weeks

What will your team do this week that might impact others?

• bug 1128768: Develop a mechanism for reporting on the behavior of categories of Flash content (e.g. Facebook video, banner ads, YouTube player, etc) in a privacy-sensitive way. No URLs or domains are ever collected
  • This will be used to evaluate performance benefits of switching certain types of Flash content to Shumway

Roundtable

(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

• All extensions will soon need to be signed – announcement: http://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience/

Links

Mailing List Threads

(Threads that are likely to be of interest to engineering from various mailing lists.)

Good Reads

(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

• Google plans to remove Chrome support for SPDY in early 2016: Hello HTTP/2, Goodbye SPDY
• Microsoft already removed IE support for SPDY in Windows 10 Technical Preview: https://twitter.com/jacobrossi/status/564877789145214976

irc #planning Log From This Meeting

---

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (lmandel)

Next Merge: February 23, 2015		Next Release: February 24, 2015
Trains
Central: 38	Aurora: 37	Beta: 36	Release: 35

• Firefox 36 Beta 6
  • Desktop shipped today
  • Mobile should ship shortly (today as well)

• Next Beta builds
  • Desktop Beta 7 gtb Thursday
    • Reviewing MSE status for 36 before gtb
  • Mobile Beta 8 gtb Monday

• Beta 36 stability is not in good shape – stability rate 2.8 and should be in the range 1.0-1.2
  • Looks like primarily gfx bugs, may be related to MSE
• Aurora 37 stability is still not in good shape – stability index is 4.9 and should be < 2.0
  • bug 1120331 (IPC, GFX-related) – 25-30% of crashes
  • bug 1123544 (gfx::GetCairoSurfaceForSourceSurface) 3.2% of crashes

• Update for OpenH264 1.3 is currently being tested on Beta, should move to release soon

Build Changes (gps)

(Build changes of which engineers should be aware.)

RelEng (catlee)

(Repo, test, and other information for engineers from the release engineering team.)

• hg -> git replication of gecko is fixed now. post-mortem happening later this week.

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

Quality Programs

(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

MemShrink (njn)

<Read Only>
No update.

Stability (kairo)

• Overall crash rates still look bad everywhere else than desktop release.
  • Esp. on Beta 36, but also Aurora 37, GFX and media/MSE crashes seem to be the highest issues, often coupled with low memory, also recently introduced shutdownhang crashes are quite high.
  • Flash crashes and hangs are sharply down, probably due to sandbox changes along with some effect from MSE.
  • Refer to today’s channel meeting notes (once they are up on the wiki) for specific bug numbers.

Team Stand-ups

(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

DOM (jst/overholt)

• Fetch landed recently (still behind pref)
• parts of Service Worker are landing
• Custom Elements (Web Components) still being figured out (https://wiki.whatwg.org/wiki/CustomElements has info and pointers)

Electrolysis (e10s) (blassey)

<Read Only>

• Please help test e10s in Nightly!
  • Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect
• We’ve reduced content-process crashes by 40%
  • See bug 1127374 and bug 1127379.
  • More fixes to come!

GFX (milan)

• Issues in Beta 36. WebGL, OOM, driver resets, unsupported combinations.

JS (naveed)

<Read Only>

• Compiler (JIT)
  • bug 1118344: (Inline SIMD.int32x4.add), bug 1112156(Unbox SIMD), bug 1112162 (Align Rectifier frames)

• Other
  • Asm.js/ARM64 now at 104 passing tests, 10 failing tests

Layout (jet/dbaron)

<Read Only>

• ImageLib regressions in FF 36 causing churn (eg. bug 1128188)
  • Landing bug 1128225 should help get us more reliable tests to avoid this in the future.
• IntegerRange template API coming soon (bug 1126552 and others)
• RTL regressions getting fixed on trunk (bug 1121748.) Already backed out of B2G2.2 and Aurora.
• W3C CSS & SVG working groups meet next week in Sydney. Contact jet, dbaron, or heycam with spec issues to resolve.
• WebKit-compatibility Fennec builds will be available for testing this week (dholbert.)

Media (mreavy)

<Read Only>

1. What has your team done since last week that might impact others?

• Landed WebRTC multistream & MSID support (a big change)
• Landed webrtc_40 update (same codebase from upstream used by Chrome 40)
• Landed PeerConnection test refactor/cleanup (reduce oranges!)
• gcp has working video (getUserMidia) sandboxing code (patch on a bug)
• OpenH264 plugin 1.3 being tested on Beta, Aurora, Nightly (but not on local dev builds)

2. What will your team do this week that might impact others?

• Looking to land renegotiation RSN (going up for review ASAP)
• OpenH264 1.3 should go to release (independent update channel from Firefox)

3. Is anything slowing your team down or getting in their way?

• Lack of time-dilation to put more hours in a day

Shumway (tschneidereit)

• Planning to enable Shumway whitelisted for IMDb and a couple other video sites.

Roundtable

(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

Links

Mailing List Threads

(Threads that are likely to be of interest to engineering from various mailing lists.)

Good Reads

(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

irc #planning Log From This Meeting

---

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (lmandel)

Next Merge: February 23, 2015		Next Release: February 24, 2015
Trains
Central: 38	Aurora: 37	Beta: 36	Release: 35

• We shipped Firefox Desktop 35.0.1 last week with a number of bug fixes

• Beta 4
  • Desktop ships today
  • Mobile ships tomorrow

• Next Beta release
  • Desktop Beta 5 gtb Thu, ships Fri
  • Mobile Beta 6 gtb Mon, ships Tue/Wed

• Significant stability issues currently on Beta and Aurora/Dev Edition. Bugs are active but may benefit from new eyes.
  • Beta
    • bug 1124880, bug 1116812, bug 1089454, bug 1124249
  • Aurora
    • bug 1120331 is 25% of all crashes

Build Changes (gps)

(Build changes of which engineers should be aware.)

RelEng (catlee)

(Repo, test, and other information for engineers from the release engineering team.)

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

Quality Programs

(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

MemShrink (njn)

• Seth Fowler has resolved a series of image-related memory usage regressions that have been present on AWSY since early November.

Stability (kairo)

<Read Only>

• Overall numbers are still bad for everything other than desktop release (see beta/devedition bugs above, nightly crash rates are even worse).

Team Stand-ups

(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

Electrolysis (e10s) (blassey)

• Please help test e10s in Nightly!
  • Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect

GFX (milan)

• WebGL regression sadness on Windows related to ANGLE. Both in 32/33 (hardware/driver specific) and 35 (investigating.) Bugs 1122465 and 1123365.
• Need to put tooling in place to see if it’s shared memory that is soft-leaking, accounting for OOM on Windows.
• Unified crashes due to driver resets, seeing crashreports at #4 which was before a long tail. Should help with tracking down the solutions.

JS (naveed)

<Read Only>

• Compiler (JIT)
  • bug 1124002: Fix a bad performance issue with closure-compiled code (by removing some code).
  • bug 1125505: Posted patches to fix mutable __proto__ to not reshape the proto chain in common cases. This should make Shumway (raytrace.swf) a lot faster.

• Front End and Other
  • bug 826741: Backtracking allocator performance work
  • Year In Review: SM in 2014 part 1: http://h4writer.com/?p=14

Layout (jet/dbaron)

• Current status of Web Animations API in Firefox: https://birtles.github.io/areweanimatedyet/
• CSS Ruby bug 1039006 will pref on once we have spec clarity (and fix) for bug 1055662
• Win64 warnings-as-errors (bug 1126017) are turning on once bug 1124029 is in the tree
• Performance profiling on Talos runs (bug 1121571)
• Work in progress on high-priority memory regression (bug 1122704)
• Backed out RTL regression (bug 1121748) for B2G 2.2 but fixing it on trunk in bug 1079154

Media (mreavy)

<Read Only>

1. What has your team done since last week that might impact others?

• bug 749703 from an external contributor broke WebRTC calls by exposing an existing bug/timing-hole (merged to m-c Saturday); a fix is about to land (bug 1126036)
  • Some end-to-end functional tests for Hello that are about to land would catch this; most in-single-browser tests as we have in mochitest suites can’t/don’t hit the timing issue introduced.

2. What will your team do this week that might impact others?

• Landing of webrtc test infrastructure bug 1119593
• Landing of webrtc Multistream support bug 1095218
• Landing of WebRTC.org update bug 1109248

Performance (vladan)

No update this week

Roundtable

(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

Links

Mailing List Threads

(Threads that are likely to be of interest to engineering from various mailing lists.)

Good Reads

(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

• Chrome 40 launches with NPAPI plugins blocked by default, removes SSL 3.0 completely. Chrome’s Flash plugin is unaffected because it uses PPAPI, not NPAPI.

irc #planning Log From This Meeting

---

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (lmandel)

Next Merge: February 23, 2015		Next Release: February 24, 2015
Trains
Central: 38	Aurora: 37	Beta: 36	Release: 35

• Firefox 35.0.1 candidates:
  • bug 1117873 – Firefox crash with “Enhanced Steam” extension since Fx35b1
  • bug 1113121 – Godaddy webmail crash [EXCEPTION_ACCESS_VIOLATION_READ]
  • bug 1121857 – document.baseURI does not get updated to document.location after base tag is removed from DOM for site with a CSP
  • bug 1122445 – CSP change in behavior regards case sensitivity loading resources

• Firefox 36 beta2 gtb Tue, ships Wed (day late due to MLK day in the US)

• Firefox 37 Aurora/Dev Edition updates have been re-enabled

• Firefox 35 post-mortem was held today. Feedback welcome at https://etherpad.mozilla.org/35-0-Post-Mortem

• lsblakk and lmandel both off the rest of this week. Sylvestre is handling all things relman.

Build Changes (gps)

(Build changes of which engineers should be aware.)

RelEng (catlee)

(Repo, test, and other information for engineers from the release engineering team.)

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

• Tree Closing Window (TCW) Saturday, January 24. Est 0700PT-1500 “Soft Close” (devs must follow up on their own jobs, intermittent outages possible.) Final details TBD. Tracking bug.

Quality Programs

(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

MemShrink (njn)

No update.

Stability (kairo)

• Crash rates currently do not look good anywhere else than desktop release. If you have any topcrash or tracked bugs filed against your team, please help getting them fixed.

Team Stand-ups

(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

Electrolysis (e10s) (blassey)

• Please help test e10s in Nightly!
  • Known issues: https://wiki.mozilla.org/Electrolysis#What_to_Expect
• bug 1118618 landed; should fix a bunch of hangs.

GFX (milan)

• No update

JS (naveed)

<Read Only>

• Compiler (JIT)
  • bug 1057082: Landed new profiler backend

• Garbage Collection
  • bug 650161: Compacting GC
    • Fixed an issue with uncollected shapes that are never touched except by compacting GC
    • Fixed several test failures and build errors
    • Attempted to land and got backed out

• Front End and Other
  • bug 1119292, bug 1119694, bug 1120207, bug 1121363: PJS removal

Media (mreavy)

<Read Only>

1. What has your team done since last week that might impact others?

• Landed (thanks to Andreas Pehrson) bug 879717 (MediaStream->video_element->canvas works again)

2. What will your team do this week that might impact others?

• Multistream support in WebRTC will reland once one problem is resolved
• Once Multistream lands and sticks, Webrtc upstream update to branch 40 will land
• Hello throttling (limits users who have the Hello button in the toolbar by default, as opposed to in Customize palette) will likely be turned to 100% within the next 1-2 weeks (everyone sees Hello in the toolbar)
• Major rewrite of WebRTC mochitests (bug 1119593)

Performance (vladan)

1. What has your team done since last week that might impact others?

• bug 1120126: Profiling Win64 nightlies should now be possible (thanks njn and dmajor)
• Reminder: 3 business days to respond to Talos regressions, 2 weeks to make decision on the regression

• If you get frequent or reproducible out-of-memory crashes (especially when Firefox is not actually out of physical memory), please ping me or David Major
• Help us test bug 998863: Asynchronous initialization of plugins
  • It’s currently preffed *OFF* by default, please help us test it: set dom.ipc.plugins.asyncInit to true
    • e10s crash issues have been fixed
  • Mark any bug reports as blockers of bug 1116806

Roundtable

(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

Links

Mailing List Threads

(Threads that are likely to be of interest to engineering from various mailing lists.)

Good Reads

(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

irc #planning Log From This Meeting

---