Channel Meeting Details

• Tuesdays and Thursdays at 10am Pacific Time
• irc.mozilla.org #planning for backchannel
• Past meeting notes: https://wiki.mozilla.org/Firefox/Channels/Meetings

Video/Teleconference Details - NEW

• 650-903-0800 or 650-215-1282 x92 Conf# 99951 (US/INTL)
• 1-800-707-2533 (pin 369) Conf# 99951 (US)
• Vidyo Room: ReleaseCoordination
• Vidyo Guest URL

Actions

Attendees

jcristau, milan, erin, jordan, philipp, RyanVM, lizzard, marcia, nicole, marco, shell, dveditz, ritu

Previous Actions

Schedule Update

• 51 is gearing up for a system add-on release to fix HSTS prefs, causing perf issues/timeouts in mixed content pages
  • HSTS priming pref flip https://bugzilla.mozilla.org/show_bug.cgi?id=1335134
  • e10s system addon also will roll out
  • system addon process: https://wiki.mozilla.org/Firefox/Go_Faster/System_Add-ons/Process

• Possible 51 dot release (later this week or early next week)

• Several Android tablets excluded from updates to 51 because of high startup crash rate: Bug 1318667
  • [philipp] staged roll-out still going on in general?

• 52.0b2 desktop + mobile released today

• 53 fennec builds were not stable till Monday; uploaded early Tuesday (jlorenzo, in EU morning)
  • What's new content was added (thanks gerry) and release notes are public

= Stability

Aurora

[marcia]

• Top crash on Aurora is an accessibility crash, despite the fact we disabled a11y+e10s in 53-> https://bugzilla.mozilla.org/show_bug.cgi?id=1333250
• Mac touchbar crash is still pretty high, #5 browser: https://bugzilla.mozilla.org/show_bug.cgi?id=1320048
  • but starting to decline after the osx 10.12.3 update \o/

Beta

awsy rate: 1.00 (browser 0.71, content 0.29)

[philipp] 52.0b1

browser crashes:

• startup crash in BaseThreadInitThunk still high: https://bugzilla.mozilla.org/show_bug.cgi?id=1322554 (5.2% of browser crashes)
  • have a reproducible case for the same signature with a particular 3rd-party program at https://bugzilla.mozilla.org/show_bug.cgi?id=1335080 (this won't cause the bulk of crashes we see though)
• (regression) shutdownhang in nsThread::nsChainedEventQueue::GetEvent https://bugzilla.mozilla.org/show_bug.cgi?id=1329966 (4.9% of browser crashes)
  • some leads in the bug, but it is stale for the past 2 weeks
• (regression) crash in @0x0 | _GetWindowIcon https://bugzilla.mozilla.org/show_bug.cgi?id=1331270 (2.3% of browser crashes)
  • crash took off after the january win patchday - bug needs investigation
• (regression) secure media bug https://bugzilla.mozilla.org/show_bug.cgi?id=1326294 (1.35% of browser crashes)
• (regression) OOM crashes with skia https://bugzilla.mozilla.org/show_bug.cgi?id=1303094 (0.9%+ of browser crashes)

content crashes:

• (regression) Crash in @0x0 | nsTimerImpl::Fire https://bugzilla.mozilla.org/show_bug.cgi?id=1323804 (6.2% of content crashes)
• (regression) Crash in nsPluginStreamListenerPeer::GetInterfaceGlobal https://bugzilla.mozilla.org/show_bug.cgi?id=1334080 (5.8% of content crashes)

Release

awsy rate 0.94 (browser 0.64, content 0.30 [marcia]

• New Kaspersky startup crash filed this morning: https://bugzilla.mozilla.org/show_bug.cgi?id=1335432
  • marco noted that these users have 2 anti-virus programs installed - maybe interfering with each other?

[philipp]

• 51 brought increase in startup crashes & strong decrease in OOM crash reports: https://crash-analysis.mozilla.com/release-mgmt/crash-report-tools/longtermgraph/?fxrel-bcat
• websense startup crash was added to the release notes and is a hot topic on sumo (3.5% of all browser crashes)
• a dozen reports on sumo from users with EMET whose tabs constantly crash - no actual crash reports are getting submitted though: https://bugzilla.mozilla.org/show_bug.cgi?id=1335086

• (no crash) single reports from users whose tab content is turning black occasionally (looks related to a particular intel gpu driver): https://bugzilla.mozilla.org/show_bug.cgi?id=1334839
  • milan says we may end up blocking that driver

Nightly

[marcia]

• Top Crash spike over the weekend - https://bugzilla.mozilla.org/show_bug.cgi?id=1334904. The bug was quickly backed out. Thanks to all that helped.
• These three signatures account for over 3500 crashes on nightly:
  • mozilla::a11y::ProxyAccessibleBase<T>::ClearChildDoc
  • mozilla::a11y::DocAccessibleParent::RemoveChildDoc
  • nsTArray_Impl<T>::IndexOf<T> | mozilla::a11y::DocAccessibleParent::RemoveChildDoc
• https://bugzilla.mozilla.org/show_bug.cgi?id=1334310 was fixed, but apparently the fix didn't work. New bug https://bugzilla.mozilla.org/show_bug.cgi?id=1334977 was opened

Mobile

[marcia]

• Release
  • Top Fennec crash https://bugzilla.mozilla.org/show_bug.cgi?id=1318667#c26
  • #3 top crash is dalvik - https://bugzilla.mozilla.org/show_bug.cgi?id=1286307
  • https://bugzilla.mozilla.org/show_bug.cgi?id=1335047 is #5 and correlated to zn-CN

Performance (Thu)

Aurora / Dev Edition

Beta

Release

QE

Beta

Action items

Mobile

RelEng

Marketing/Communications

User Advocacy

Roundtable

• (liz) we have some data from rhelmer yesterday that may mean hotfix uptake is as high as 90%
  • should have data from his analysis of system addon uptake that will tell us more....
  • for now, sticking with system addons (for current issues on release) as we aren't sure of the effectiveness/uptake
  • if we do a dot release we can uplift his diagnostic patches to get more info on uptake
  • meta bug here https://bugzilla.mozilla.org/show_bug.cgi?id=1323547

What are we doing about geolocation not working on 51 (windows) (liz: This works now on release afaik) https://bugzilla.mozilla.org/show_bug.cgi?id=1333516

• • jlund: afaict, we serve all users including windows to 51.0.1 (version which includes geolocation fix). iow - we are not holding windows users back to <51.0

Got it! Thank you

Special Topics

Aurora/Beta Feature Review

Post-Mortem (Tues 2wks from GA Release)

• https://public.etherpad-mozilla.org/p/51-0-Post-Mortem - Feb 7th?

Sign Off (Thurs prior to GA Release)

Actions