Firefox/Channels/Meetings/2017-03-30
Channel Meeting Details
- Tuesdays and Thursdays at 10am Pacific Time
- irc.mozilla.org #planning for backchannel
- https://wiki.mozilla.org/Firefox/Channels/Meetings for archives
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
Contents
Attendees
lizzard, jcristau, jlorenzo,ninu,petruta, philipp, Timea, RyanVM, Oana,Cornel, Iulia, nicole, Sorina, Florin, Camy
Previous Actions
Schedule Update
- root cause for fallback update test failures still unclear, but most likely not an issue in firefox, so 52.0.2esr and 53.0b7 unblocked yesterday
- 52.0.2esr, 52.0.2 desktop and fennec, 53.0b7 desktop and fennec shipped
Add-ons
Stability
Shutdownkill crash spike in early March (this is the infobar thing switched on?) https://crash-stats.mozilla.com/signature/?signature=IPCError-browser%20%7C%20ShutDownKill&date=%3E%3D2017-02-28T14%3A57%3A21.000Z&date=%3C2017-03-30T14%3A57%3A21.000Z#graphs
- yes, infobar on the beta channel - same happened at the start of the 52 cycle: https://crash-stats.mozilla.com/signature/?release_channel=beta&signature=IPCError-browser%20%7C%20ShutDownKill&date=%3E%3D2016-12-30T15%3A02%3A25.000Z&date=%3C2017-03-30T15%3A02%3A25.000Z#graphs
Aurora
awsy rate: 4.43 (browser 1.01, content 3.42) telemetry (m+c-s) from sunday: 2.81 (was 3.01 the week before, 2.63 this time last cycle)
[marcia]
- Not much new to report since Tuesday - https://bugzilla.mozilla.org/show_bug.cgi?id=1349847 is still the top overall browser crash
Beta
awsy rate: 0.85 (browser 0.55, content 0.30) telemetry (m+c-s) from sunday: 3.10 (was 2.99 the week before, 5.18 this time last cycle)
[philipp] not much data from b7 yet, so the top stability issues remain the ones raised on tue: https://wiki.mozilla.org/Firefox/Channels/Meetings/2017-03-28#Beta
other noteworthy crashes:
- Crash in igd10iumd32.dll | CContext::EmptyOutAllDDIBindPoints: https://bugzilla.mozilla.org/show_bug.cgi?id=1351349 (0.35% of browser crashes, volume doubled in the 53 cycle)
- Crash in std::map<T>::_Try_emplace<T>: https://bugzilla.mozilla.org/show_bug.cgi?id=1351993 (0.1% of browser crashes; regressing in 53 - something seams to have fixed it in the 54 nightly cycle)
Release
awsy rate: 0.78 (browser 0.57, content 0.21) telemetry (m+c-s) from sunday: 2.45
[marcia]
- Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1351728 which showed up on the explosiveness report on 52. Only affects Mac 10.12 users and is #36 overall top browser crash. Maybe related to plugging in headsets.
Nightly
awsy rate: 15.31 (browser 2.44, content 12.86) telemetry (m+c-s) from sunday: 13.15 (was 12.54 the week before, 9.18 this time last cycle)
[marcia]
- Filed new crash https://bugzilla.mozilla.org/show_bug.cgi?id=1352047
- More webrender crashes such as mozilla::ipc::MessageChannel::Send | mozilla::layers::PWebRenderBridgeChild::SendDPBegin
- Milan says not to worry, people are force enabling the pref
Mobile
awsy rate: 1.16
Performance (Thu)
Aurora / Dev Edition
Beta
Release
QE
[Andrei]
- Disable network predictor prefetch system add-on (1351082) - QA currently blocked due to corrupted xpi.
- A bunch of testing sessions planned next week for: Creators Update (Fx53), e10s-Multi (Fx54) and Sandbox Flash on 64-bit Windows (Fx54).
- We'll tag any new issues with the [Creators] string in their summaries.
- (read-only) pre-Aurora and pre-Beta sign offs are scheduled to be completed by next Friday, Apr 7.
Nightly
Aurora / Dev Edition
Beta
- [Andrei] Pre-Release feature sign offs are in progress (estimate of completion: Fri, Mar 31). Preliminary assessments below:
- [Alex] Compositor Process for Windows - Sign-off currently depends on uplifting the fixes for bug 1331548 and bug 1331761 + found new bug in google maps (bug 1352081)
- [Petruta] Send stack traces for each content crash to the crash manager - signed off without issues
- [Timea] Reader Mode Displays Estimated Reading Time -Sign off with GREEN status, there are no issues found during sign off testing, it is one known bug (1340502) which is no blocker
- [Cristian] Stopped Exporting XPCOM Symbols - Sign off with GREEN status, as only one known issue found during testing, however it is not severe enough to block the testing ( bug 1312899 )
Action items
Mobile
- [Ninu]
- Signed off the 52.0.2 build on Monday with no major issues
- Signed off the 53.0b7 build on Tuesday with no blocking issues
New bug logged during testing session bug 1351308 - Downloads are not cleared on exit (https://bugzilla.mozilla.org/show_bug.cgi?id=1351308)
Performance
RelEng
Marketing/Communications
User Advocacy
Roundtable
[mahe] Any testing blocker for validating SUMO links? SSL cert related?