Firefox/Channels/Meetings/2018-02-13
From MozillaWiki
Channel Meeting Details
- Tuesdays 10am and Thursdays at 8am Pacific Time
- irc.mozilla.org #planning for backchannel
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: Release Coordination
- Vidyo Guest URL
REMEMBER
These notes are read by people who weren't able to attend the meeting. Please make sure to include links and context so they can be understood.
Contents
Attendees
marcia, julien, ben, philipp, Aryx, Tom ,Thomas, tjr, Milan, dveditz
Previous Actions
Schedule Update
Current releases dashboard: https://mozilla.github.io/delivery-dashboard
- Firefox 58.0.2 went to 100% today
- Firefox for Android 58.0.2 is at 100% staged rollout on GooglePlay
- Firefox 59.0b9 signoffs are ready
Add-ons
Shield studies
- FYI: Shield studies in flight. https://gregglind.github.io/x-shield-inflight-dashboard
Stability
- Important Note: Nightly AWSY rates are inflated due to an ADI Issue
Nightly
awsy rate: 7.39 (browser 2.89, content 4.50) telemetry (m+c-s) from sunday: 3.31 (week before: 3.25, this time last cycle: 7.39)
[marcia]
- Regression in Core|XPCOM is now fixed: https://bugzilla.mozilla.org/show_bug.cgi?id=1437114
- New webrender issue https://bugzilla.mozilla.org/show_bug.cgi?id=1437886
- Nightly crash triage has been fairly quiet: https://wiki.mozilla.org/NightlyCrashTriage/2018Q1
Beta
awsy rate: 0.66 (browser 0.36, content 0.30) telemetry (m+c-s) from sunday: 1.90 (week before: 1.76, this time last cycle: 2.24)
[marcia]
- #3 top crash https://bugzilla.mozilla.org/show_bug.cgi?id=1424505 is still hanging around. - 10.5% of browser crashes
[philipp]
- crashes with greyware rlls64.dll/pmls64.dll modules: https://bugzilla.mozilla.org/show_bug.cgi?id=1394550 - 3% of browser crashes
- vendor claims they are starting to roll-out a fix
- IPC crashes related to printing: https://bugzilla.mozilla.org/show_bug.cgi?id=1432409 - 2.4% of content crashes
- uplift of bug 1422036 into beta 8 to address parts of the common mozilla::dom::workers::RuntimeService::CrashIfHanging shutdownhang signature (18% of browser crashes) didn't yield any obvious results
Release
awsy rate: 0.70 (browser 0.36, content 0.34) telemetry (m+c-s) from sunday: 1.66 (week before: 1.52, this time last cycle: 1.48)
Mobile
awsy rate: release 0.52 - beta 0.71 - nightly 19.47
- Release
- Nothing important to note
- Beta
- Top crashes are on file. Nothing important to call out. There are a few unfiled, small volume crashes that are only on specific handsets or older APIs
- Nightly
- https://bugzilla.mozilla.org/show_bug.cgi?id=1437436 has moved up to the top crash on nightly and has caused rate to rise
- Scrolling regression which started in 2/4 build: https://bugzilla.mozilla.org/show_bug.cgi?id=1437515
Performance (Thu)
Aurora / Dev Edition
Beta
Release
QE
Nightly
Aurora / Dev Edition
Beta
Action items
Mobile
Performance
RelEng
- WebSense updates were unblocked for ~24h - how do figure out if it's okay to unblock them permanently?
- no apparent crashing problems in recent release builds after unlocking updates for known websense users on 47: https://crash-stats.mozilla.com/search/?proto_signature=~qipcap.dll&proto_signature=~qipcap64.dll&release_channel=release&date=%3E%3D2018-02-12T01%3A00%3A00.000Z&_facets=signature&_facets=version#facet-version
