Confirmed users
3,314
edits
(15 intermediate revisions by 9 users not shown) | |||
Line 30: | Line 30: | ||
|Release: {{RELEASE_VERSION}} | |Release: {{RELEASE_VERSION}} | ||
|} | |} | ||
* 32.0.1 updates disabled today, maybe 32.0.2...we'll see | |||
** candidate driver: {{Bug|1063052}} Firefox 32 startup crash in nsFrame::BoxReflow | |||
* Beta4 desktop releases today, mobile tomorrow | |||
* Beta5 (desktop) go to build Thursday | |||
* Beta6 (desktop and mobile) go to build Monday | |||
===Build Changes (gps)=== | ===Build Changes (gps)=== | ||
Line 56: | Line 62: | ||
===Stability (kairo)=== | ===Stability (kairo)=== | ||
* 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}}). | |||
* 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 89: | Line 98: | ||
===Desktop Platform (bsmedberg)=== | ===Desktop Platform (bsmedberg)=== | ||
<!-- Read only update this week? Uncomment the following line--> | <!-- Read only update this week? Uncomment the following line--> | ||
{{readonly}} | |||
Mac V2 signing work is our top priority and we hope to have that on nightly next week. | |||
===Developer Tools (prouget)=== | ===Developer Tools (prouget/bgrins)=== | ||
* New Timeline devtool has landed. See post and screenshot: https://groups.google.com/d/msg/mozilla.dev.gaia/IT-M42uGT40/_cV31uMY9fcJ | |||
* New Timeline | * Announced Safari/Chrome protocol support in Firefox devtools: https://hacks.mozilla.org/2014/09/firefox-tools-adapter/ | ||
* | * Hacks post with release notes for 34: https://hacks.mozilla.org/2014/09/webide-storage-inspector-jquery-events-iframe-switcher-more-firefox-developer-tools-episode-34/ (WebIDE, Storage inspector, jQuery events, iframe switcher) | ||
===DOM (jst/overholt)=== | ===DOM (jst/overholt)=== | ||
Line 122: | Line 132: | ||
* You can see the status of the current iteration (35.1) in progress [https://docs.google.com/a/mozilla.com/spreadsheets/d/10sr6YhDNmO4oimlNtxDZ5fe6IaQKmZ7gqT-ZWqAygrI/edit#gid=1914765814 here] | * You can see the status of the current iteration (35.1) in progress [https://docs.google.com/a/mozilla.com/spreadsheets/d/10sr6YhDNmO4oimlNtxDZ5fe6IaQKmZ7gqT-ZWqAygrI/edit#gid=1914765814 here] | ||
====Summary of Recent Landings==== | ====Summary of Recent Landings==== | ||
* Team landed | * Team landed 42 bugs over the last week, to close out the 35.1 iteration. | ||
* Details of landings from the past week can be seen [https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&list_id=11140065&o1=substring&resolution=FIXED&o2=substring&chfieldto=Now&chfield=resolution&query_format=advanced&chfieldfrom=2014-09-09&f2=flagtypes.name&chfieldvalue=FIXED&v1=firefox-backlog&v2=%2B here] | * Details of landings from the past week can be seen [https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&list_id=11140065&o1=substring&resolution=FIXED&o2=substring&chfieldto=Now&chfield=resolution&query_format=advanced&chfieldfrom=2014-09-09&f2=flagtypes.name&chfieldvalue=FIXED&v1=firefox-backlog&v2=%2B here] | ||
Line 128: | Line 138: | ||
<!-- Read only update this week? Uncomment the following line--> | <!-- Read only update this week? Uncomment the following line--> | ||
<!-- {{readonly}} --> | <!-- {{readonly}} --> | ||
====Work In Progress==== | |||
* Browser toolbar refresh {{bug|1058909}} | |||
* WebRTC OpenGL on Roku - fixing and tweaking | |||
* Moz Stumbler currently off due to start time regression {{bug|1064677}} | |||
*Janus https://wiki.mozilla.org/Mobile/Janus | |||
**investigating performance issues | |||
**looking into <picture> element injection | |||
**Adding TCP/socket stats | |||
You can find more on upcoming feature plans in the[[https://wiki.mozilla.org/Mobile/Roadmap| roadmap]] | |||
====Landings from the past week==== | |||
===== Nightly ({{CENTRAL_VERSION}})===== | |||
*Lightweight theme preview is broken ([https://bugzilla.mozilla.org/show_bug.cgi?id=887755 Bug 887755 ]) | |||
*Synchronous initialization of search service when handling open search tag ([https://bugzilla.mozilla.org/show_bug.cgi?id=1017903 Bug 1017903 ]) | |||
*[Roku] Removing an entry from history will only take effect after restarting the Roku app ([https://bugzilla.mozilla.org/show_bug.cgi?id=1025923 Bug 1025923 ]) | |||
*crash in java.lang.NullPointerException: at org.mozilla.gecko.home.PinSiteDialog$3.onFocusChange(PinSiteDialog.java) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1041448 Bug 1041448 ]) | |||
*crash in mozilla::layers::TileClient::GetBackBuffer(nsIntRegion const&, mozilla::layers::TextureClientPool*, bool*, bool) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1041744 Bug 1041744 ]) | |||
*about:home is unresponsive to hardware menu button on returning to main activity on 2.3 devices ([https://bugzilla.mozilla.org/show_bug.cgi?id=1058027 Bug 1058027 ]) | |||
*Regression: Back button icon missing in menu on some small screen (?) hardware (?) devices ([https://bugzilla.mozilla.org/show_bug.cgi?id=1062338 Bug 1062338 ]) | |||
*"Learn More" link for the Mozilla Location Service is visible on Beta/Release despite MLS setting not available ([https://bugzilla.mozilla.org/show_bug.cgi?id=1063518 Bug 1063518 ]) | |||
*crash in webrtc::ViEInputManager::NumberOfCaptureDevices() ([https://bugzilla.mozilla.org/show_bug.cgi?id=1063547 Bug 1063547 ]) | |||
*[roku] update wording in the public roku channel app ([https://bugzilla.mozilla.org/show_bug.cgi?id=1064222 Bug 1064222 ]) | |||
*Search activity startup crash @ java.lang.IllegalArgumentException: Couldn''t find search engine for identifier: yahoo at org.mozilla.search.providers.SearchEngineManager.createEngine(SearchEngineManager.java) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1065123 Bug 1065123 ]) | |||
*crash in java.lang.NoSuchMethodError: android.os.Bundle.getString at org.mozilla.gecko.preferences.GeckoPreferences.setupPreferences(GeckoPreferences.java) ([https://bugzilla.mozilla.org/show_bug.cgi?id=1065531 Bug 1065531 ]) | |||
*Regression: Downloading is broken ([https://bugzilla.mozilla.org/show_bug.cgi?id=1066671 Bug 1066671 ]) | |||
===Firefox OS Communications (scravag)=== | ===Firefox OS Communications (scravag)=== | ||
Line 198: | Line 232: | ||
===JS (naveed)=== | ===JS (naveed)=== | ||
{{readonly}} | |||
* Compiler (JIT) | |||
** {{bug|1062869}}: Add ability to execute recover instructions ahead of bailouts. This improves Scalar Replacement for arguments given to multi-basic-block inlined functions. This also one step forward to "eager" escape analysis. | |||
** {{bug|894596}}: Patch to allow inlining global variable values. Investigating possible performance regressions associated with the patch. | |||
* Garbage Collection | |||
** {{bug|1020751}} and {{bug|1022794}}: Enabled GGC for B2G | |||
* Front End and Other | |||
** SIMD lands in Nightly. Firefox demoed running JS-SIMD on stage at IDF 2014. [http://sunfishcode.github.io/blog/2014/09/09/js-simd.html Dan Gohman's JS-SIMD blog post] | |||
** {{bug|1064451}}: eliminated the function-call in every MOZ_ASSERT expansion | |||
===Layout (jet/dbaron)=== | ===Layout (jet/dbaron)=== | ||
Line 207: | Line 251: | ||
===Media (mreavy)=== | ===Media (mreavy)=== | ||
<!-- Read only update this week? Uncomment the following line--> | <!-- Read only update this week? Uncomment the following line--> | ||
{{readonly}} | |||
* Fixed problem with Webrtc and H.264 under very high packet loss (bug 1054624) | |||
* Resolved Screensharing issues on Windows due to multiple threads (MediaManager, D3D9 in gfx/compositor) which made windows calls without running on a Windows messageloop - thanks jimm! | |||
* working on policy for additions to screensharing whitelist | |||
* ScreenSharing now *must* occur from an https: site for security/privacy reasons | |||
===Necko (dougt/jduell)=== | ===Necko (dougt/jduell)=== | ||
<!-- Read only update this week? Uncomment the following line--> | <!-- Read only update this week? Uncomment the following line--> | ||
{{readonly}} | |||
* No update this week. | |||
===Performance (vladan)=== | ===Performance (vladan)=== | ||
<!-- Read only update this week? Uncomment the following line--> | <!-- Read only update this week? Uncomment the following line--> | ||
<!-- {{readonly}} --> | <!-- {{readonly}} --> | ||
Update next week | |||
===Seceng (grobinson)=== | ===Seceng (grobinson)=== | ||
Line 246: | 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> |