Confirmed users
3,314
edits
(2 intermediate revisions by one other user not shown) | |||
Line 62: | Line 62: | ||
===Stability (kairo)=== | ===Stability (kairo)=== | ||
* We just halted 32.0.1 updates due to bug 1063052. | * We just halted 32.0.1 updates due to {{bug|1063052}}. | ||
* Beta still has GFX issues on both desktop (OMTC/D3D11) and Android (AlphaBoxBlur bug 1028802). | * Beta still has GFX issues on both desktop (OMTC/D3D11) and Android (AlphaBoxBlur {{bug|1028802}}). | ||
* Prompt for e10s on Nightly triggered us seeing a lot of e10s crashes, we need a lot of work there until we'll be able to ship anything there or even turn on by default. | |||
==Team Stand-ups== | ==Team Stand-ups== | ||
Line 298: | Line 299: | ||
===irc #planning Log From This Meeting=== | ===irc #planning Log From This Meeting=== | ||
<pre style="white-space:pre-wrap;"> | <pre style="white-space:pre-wrap;"> | ||
11:02 cpeterson: https://wiki.mozilla.org/Platform/2014-09-16 | |||
11:05 bsmedberg: blassey: jimm: I'll be following up with you later about the e10s crashes | |||
11:05 blassey: ok | |||
11:06 lmandel: bsmedberg: I see readonly update about v2 sigs. Do you want to tell people what that means? | |||
11:06 cpeterson: e10s content crashes are up about 100x since the e10s opt-in prompt | |||
11:06 bsmedberg: lmandel: not really, do you think I need to? | |||
11:06 lmandel: bsmedberg: Only if you think people will be impacted in their work. | |||
11:07 lmandel: bsmedberg: We should probably call out when this is done so that people know. | |||
11:07 KaiRo: hmm, do I only voip badly in those larger meetings? I didn't hear complaints in the smaller ones I'm usually in | |||
11:07 bsmedberg: I think rstrong will be sending an email around to dev.platform when the current oranges/issues are solved before we actually flip things over | |||
11:07 lmandel: KaiRo: You were fine in the channel meeting. | |||
11:07 lmandel: bsmedberg: k | |||
11:08 KaiRo: lmandel: ok, maybe the added traffic of more people on the meeting tips it over or so | |||
11:09 KaiRo: btw, "Firefox is not starting now" seems to be a quite common issue with e10s | |||
11:09 armenzg_mtg: cpeterson, I will mention it here | |||
11:09 armenzg_mtg: I tried e10s on Linux Desktop nightly recently and it was a pretty awful experience | |||
11:10 armenzg_mtg: enabling it by default even for one day will be pretty terrible for nightly testers | |||
11:10 KaiRo: snorp: did you get a crash reporter at all for that non-starting thing with e10s? | |||
11:10 snorp: KaiRo: yeah, standby, will paste | |||
11:11 snorp: https://crash-stats.mozilla.com/report/index/c5ef1fca-fde0-44c8-95ef-680052140916 | |||
11:11 KaiRo: snorp: ok, good to know, startup crashes sound like the first thing we need to fix | |||
11:11 snorp: yes. | |||
11:11 armenzg_mtg: cpeterson, what is the preferred way to give feedback about e10s? | |||
11:11 KaiRo: xpc::AddonWindowOrNull | |||
11:11 KaiRo: sounds like fun with add-ons | |||
11:12 cpeterson: armenzg_mtg: you can mention e10s problems in #e10s or just file a bug. Be sure to include the word "e10s" in your bug summary so our e10s triage queries will find it! | |||
11:13 dveditz: armenzg: there's a link to file bugs at https://wiki.mozilla.org/Electrolysis#Contributing | |||
11:13 armenzg: cpeterson, dveditz thank you gentlemen - I will dog food again | |||
11:13 dveditz: also descriptions of known issues and links to known bugs for dupe finding | |||
11:13 dveditz: on that page | |||
11:13 dveditz: I mean a link to a query | |||
11:14 KaiRo: snorp: can you file this one? sounds like this specific signature only exists today | |||
11:14 snorp: KaiRo: https://bugzilla.mozilla.org/show_bug.cgi?id=1068163 | |||
11:14 cpeterson: armenzg: TBH, if you had e10s crash problems, you might want to wait a day before dogfooding again for some recent fixes to make their way to mozilla-central and then Nightly builds. | |||
11:15 KaiRo: snorp: awesome, thanks. the signature seems to be all only today's build. fun. | |||
11:15 snorp: KaiRo: yay | |||
11:15 armenzg: cpeterson, I'm good with crashes - IIRC I was having responsiveness issues | |||
11:15 cpeterson: armenzg: oh, that problem has not been fixed yet <:) | |||
11:15 snorp: heh | |||
11:15 snorp: cpeterson: what causes it | |||
11:16 snorp: shouldn't it be *more* responsive | |||
11:16 armenzg: cpeterson, k thanks | |||
11:16 armenzg: snorp, in some cases :P | |||
11:16 cpeterson: snorp: I don't know the cause, but there is likely some IPC bottleneck between parent and content process. | |||
11:17 cpeterson: snorp: the browser should be more responsive (because its UI thread is not blocked on content as much), but all tabs run in the same process that can block each other. | |||
</pre> | </pre> |