Firefox/Channels/Meetings/2016-09-27

« previous week | index | next week »

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

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.

Attendees

RyanVM, Rail, Milan, Calixte, Marco, Julien, Callek, ritu, philipp, Kevin, Liz, shell, dveditz, davidb

Schedule Update

• 49.0.1 released on Friday.
  • Mac/Linux users on 49.0 stay there, Mac/Linux from < 49 update to 49.0.1
  • websense update situation: we should try soon to bring the "unknown" status users from 47 to 49

• No current driver for 49.0.2. If you have a suggestion for one please let Liz know so we can mark it as a blocker.

• Beta50
  • 50.0b2 pushed to Beta channel
  • Waiting for sign offs on Fennec 50.0b2

Stability

Beta

overall rate 1.23 (browser 0.97, content 0.26)

[philipp] 50.0b1

• content crash rate is douple of what it has been in 49.0b:
  • Crash in IPCError-browser | (msgtype=0xAE0005,name=PNecko::Msg_PHttpChannelConstructor) Value error: message was deserialized, b https://bugzilla.mozilla.org/show_bug.cgi?id=1289001 (12.6%)
  • Crash in IPCError-content | (msgtype=0xC2000A,name=???) Route error: message sent to unknown actor ID https://bugzilla.mozilla.org/show_bug.cgi?id=1290766 (11.7%)
• browser crashes:
  • Crash in DisconnectSwitch/COIDTable::ThreadCleanup https://bugzilla.mozilla.org/show_bug.cgi?id=1294903 (3.5%)
    • We have a windows7 developer from Microsoft engaged. He is requesting crash dumps or repro steps. How do we proceed? None of the comments help.
    • Kevin suggested looking for email addresses in the crash dumps.
    • Invite a bay area MS employee to come onsite, talk to Legal.
    • this one is also having a distinct weekday (high crash volume) - weekend (low volume) pattern
  • Crash in std::list<T>::clear() from D2D1::EndDraw() https://bugzilla.mozilla.org/show_bug.cgi?id=1291084 (2.2%)
    • 64bit only? https://bugzilla.mozilla.org/show_bug.cgi?id=1291084#c27
  • Crash in gfxASurface::Wrap https://bugzilla.mozilla.org/show_bug.cgi?id=1305234 (1.3%)
    • fixable with a backout
  • Intel cpu specific crashes in arena_dalloc_small... are back as well https://bugzilla.mozilla.org/show_bug.cgi?id=1296630 (6.3%)
• also got a couple of bugs for lower-volume regressing crashes on file

Release

overall rate 0.97 (browser 0.79, content 0.18)

• #3 topcrash on release with 1.44% of total crashes. Shutdown hang/crash
  • Bug 1292311 - Crash in nvwgf2um.dll | NDXGI::CDevice::DestroyDriverInstance
  • Related to Bug 1285333 - Crash in atidxx32.dll | atiuxpag.dll | CContext::EmptyOutAllDDIBindPoints
  • speculative patch in Bug 1296749 - Fix DirectX shutdown order

• Websense crash still present but not bad: https://crash-stats.mozilla.com/signature/?signature=PREF_GetIntPref

[philipp] the proportion of content crashes has been rising in the past days - it would be intersting to know how the percentage of e10s users on release is developing...

• • Erin said it's ~26 million end-users with e10s on release channel.
  • Not seeing difference for add-ons e10s stability - 3rd chart (main crash) is showing some uptick (but low numbers) with and without add-ons (asking folks for thoughts) https://sql.telemetry.mozilla.org/dashboard/stability-metrics-for-e10s-add-ons-experiment-release-49-
  • ADI based: https://crash-analysis.mozilla.com/rkaiser/crash-report-tools/longtermgraph/?fxrel (uncheck Combine browser+content to see content crash rate developing)

Nightly

[marcia]

Mobile

• accounts for ~33% of B1 crashes https://bugzilla.mozilla.org/show_bug.cgi?id=1304777
  • Kevin suggested we block on this startup crash and not push Beta2
• release numbers are around 1.0 crash/100 ADI a new best \o/

QE

Mobile

==Performance

User Advocacy

recurring user feedback on sumo about 49 update:

• users not able to open firefox
  • with missing mozglue.dll or 0xc0000022 error; pretty sure this is tied to avg: https://bugzilla.mozilla.org/show_bug.cgi?id=1304848 (Liz wrote to AVG contact this morning)
  • failing silently (firefox.exe process running without much resources used, but UI not opening): https://bugzilla.mozilla.org/show_bug.cgi?id=1305436 (asking Jimm to help find someone to work with SUMO to investigate)
    • Sounds similar to recent Trusteer issue? (bug 1300545) - users posted their list of installed programs & trusteer was not among them :-(
• graphics artefacts (win10) & vertical lines when scrolling down (win7, vista)

Roundtable

• (liz) If you are curious about websense and current update status, here is a description
  • https://public.etherpad-mozilla.org/p/rmhDxOn0q7
  • Rail's useful table of who gets served which version: https://docs.google.com/spreadsheets/d/1Hkz6q-LVUC6qKy0Ug9dFBFLYvz4__U2rhDtUOpywDus/edit#gid=0
  • Desigan is working with legal to get us test licenses from Websense.
  • Brad mentioned two more ideas on how we can tackle the Websense crashes.

Special Topics

Post-Mortem (Tues 2wks from GA Release)

• Next Tuesday Oct 4 -- Please add your thoughts to the etherpad !
  • https://public.etherpad-mozilla.org/p/49-0-Post-Mortem
  • Is this a post-mortem for 48 as well?