Notices/Schedule (lsblakk/sylvestre/lmandel)

Build Changes (gps)

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.)

Stability (kairo)

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.

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.)

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.)

Build Changes (gps)

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.)

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.)

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.)

38 Nightly will be the next ESR. Get your refactorings or other major changes in while 38 is on m-c.

A note on branching:

FXOS v2.2 update : Please note that has diverged from mainline gecko and is on its own b2g37 branch. mozilla-aurora (gecko 37) will continuously be merged to mozilla-b2g37_v2_2 . So, if you have a gecko bug that you are fixing on aurora and impacts b2g as well, you do not have to worry about requesting approval twice as the sheriff’s will auto-merge it for you.

Want all merge and release days included in your calendar? Add this Google calendar.

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.)

The next Tree Closing Window (TCW) is scheduled for Saturday, January 24. The list of work is not yet finalized, more detail on time impact next week.

Quality Programs

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

MemShrink (njn)

Stability (kairo)

<Read Only>

Waiting for data on new versions, a lot of 36 beta focus will be on MSE crashes.

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)

We will be disabling Flash protected mode for FF36beta1 (Desktop) and evaluating stability metrics and looking for regressions. We have not yet made a decision about whether this will ship to release.

There appears to be a bug where our hook is ineffective on Windows 8.1.

Next week we’ll be doing a throttling change where the plan (unless there are known issues in the wild) will be to enable updates at 100% on Friday Jan 16th (4 days earlier than current)

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>

DMD is now working reliably on Mac, and also seems to be working on Fennec. Follow the instructions and try it out!

Stability (kairo)

bug 1088148 is a supposed a11y crash fix that triggered a huge spike in its own crash signature. This is 1/3 of current Nightly crashes!

bug 1116825 was a significant plugin crash spike, but fix should just have landed.

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)

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

bug 1110215: Disabled Flash protected mode on Beta as an experiment. See bug 1111791 for a report on the results.

b) Many Telemetry measurements are biased by users who submit many short sessions (vs users with fewer, longer sessions). You can remove this bias by doing your analysis “per user” using the new clientID field:

Notices/Schedule (lsblakk/sylvestre/lmandel)

[READ ONLY] – Beta 6 Desktop and Mobile builds are with QA, should ship later today. No further beta builds planned this week.

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)

No update.

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.)

Stability (kairo)

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.)

A*Team (jgriffin)

All of this was announced in dev.platform and dev.b2g but here’s your chance to ask questions

k18e’s team is planning to uplift some media rewrites being done by alfredo and blake wu.

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

GMail/Gcal

Necko (dougt/jduell)

HTTP/2 is scheduled to land on FF 35 (we’ll advertise draft spec only)

we’ll advertise final (non-draft) HTTP/2 support in 36

opportunistic encryption will be in 37

B2G emulator still appears to be broken (pipe writes can get lost)

we’re trying to hack around it for our fix

Performance (vladan)

<Read Only>

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.)

irc #planning Log From This Meeting

10:52 AM <KaiRo> lmandel: looks like I found the issue behind the gfx issues on beta, see https://bugzilla.mozilla.org/show_bug.cgi?id=1097321#c26
10:53 AM <KaiRo> and lsblakk ^^^
10:55 AM <lmandel> KaiRo: Good sleuthing.
10:56 AM <KaiRo> lmandel: luckily I just stumbled over bugmail of SoftVision verifying that bug that seems to have caused the issue ;-)
10:57 AM <KaiRo> and that got me thinking "hey, we did just land unblocking something that includes Intel stuff? wait a minute..." ;-)
11:00 AM <KaiRo> lsblakk: actually, 1) sheriffs/RyanVM can do a straight backout right away if we are sure enough, that doesn't even need Jeff, and 2) I'm actually reluctant to sign off 35.0b4 with this huge startup crash issue continued
11:00 AM <•lsblakk> ah, didn't see that it was a startup crash anywhere until now
11:00 AM <•lsblakk> in that case, i'm happy to take a backout and do a build 2
11:03 AM <overholt> cpeterson, did milan_ and I get disconnected?
11:03 AM <KaiRo> lsblakk: yes, took me a bit to realize as well, I'm definitely in favor of a build2 there.
11:04 AM <cpeterson> overholt: i don't see you guys on screen
11:04 AM <overholt> cpeterson, thanks. looks like a Vidyo crash. we're back.
11:04 AM <Pike> not just that the calendars are all upset, my head thinks it's wednesday, too
11:07 AM <RyanVM|sheriffduty> KaiRo: lsblakk: backing out now
11:07 AM <KaiRo> RyanVM|sheriffduty: thanks
11:10 AM <RyanVM|sheriffduty> jduell: CC me to that bug when you file it?
11:10 AM — RyanVM|sheriffduty wonders if that's the same underlying issue we have with other emulator test stability issues
11:11 AM <jduell> RyanVM|sheriffduty: will do
11:11 AM <RyanVM|sheriffduty> thanks
11:11 AM <jesup> jduell: sorry, we don't detect it directly: #if defined(MOZ_WIDGET_GONK) && defined(DEBUG) // B2G emulator debug is very, very slow and has problems dealing with realtime audio inputs
11:11 AM <jduell> jesup: ah. Ok, thanks
11:13 AM <jduell> jesup: hmm, this looks interesting... http://mxr.mozilla.org/mozilla-central/source/gfx/thebes/gfxAndroidPlatform.cpp#117

We’re still working on split apk for Gingerbread users, should have that in place in the next couple of weeks

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>
No update.

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.)

Work moving forward towards multiple streams of a type and renegotiation

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

Starting work towards a webrtc.org update

More sdparta work

Performance (vladan)

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

bug 1107779, bug 1107782: Avi found that the “activeTicks” FHR measurement significantly over-reports Firefox usage time, because Firefox fires “user-interaction-active” notifications while the mouse cursor is positioned over the browser even when the user is away from the computer

Should we just land the fix, or is it important to maintain continuity with the current measurement (for monitoring for relative changes)?

The above bugs are unrelated to the big drop in activeTicks reported in bug 1096498