Electrolysis/Meetings/2016-09-22: Difference between revisions
< Electrolysis | Meetings
Jump to navigation
Jump to search
(felipe) |
(→mconley: Add mconley stuff.) |
||
| Line 16: | Line 16: | ||
** I think billm and I are going to split up {{bug|1303077}} to try to get main thread stacks from the content process when the spinner is shown for a while. | ** I think billm and I are going to split up {{bug|1303077}} to try to get main thread stacks from the content process when the spinner is shown for a while. | ||
** [https://www.reddit.com/r/firefox/comments/53srkq/new_loading_icon_when_a_page_in_a_new_tab_is/ More reports of spinner on Reddit.] I'm engaging with the user. | ** [https://www.reddit.com/r/firefox/comments/53srkq/new_loading_icon_when_a_page_in_a_new_tab_is/ More reports of spinner on Reddit.] I'm engaging with the user. | ||
* Could be some cases where spawning content processes takes longer on some systems? See {{bug|1304393}} and [https://vimeo.com/183656814 and this video]. | |||
** User had no add-ons. Looks like the content process is taking its sweet time getting started. Profile is useless because the problem is solved by the time the profiler backend starts working in the content process. | |||
==chutten== | ==chutten== | ||
Revision as of 16:00, 22 September 2016
« previous week | index | next week »
mconley
- bug 1300411 - user reports excessive load spinning when switching tabs with e10s in 48.0.2 release
- gps pointed me at UIforETW as a way of getting really nice, low-level cross-process profiles, using a nicer front-end for Microsoft's Event Tracing infrastructure.
- Instructions to point users to.
- billm's patch from bug 1279086 landed last week (and just made uplift!). Still waiting on Telemetry data to saturate and give us a few more days worth, but...
- I think billm and I are going to split up bug 1303077 to try to get main thread stacks from the content process when the spinner is shown for a while.
- More reports of spinner on Reddit. I'm engaging with the user.
- Could be some cases where spawning content processes takes longer on some systems? See bug 1304393 and and this video.
- User had no add-ons. Looks like the content process is taking its sweet time getting started. Profile is useless because the problem is solved by the time the profiler backend starts working in the content process.
chutten
bytesized
- bug 1301452 - (tab switcher telemetry probe test) finished and checked in.
felipe
- bug 1304113 - Change tab switching telemetry probes to be opt-out
- bug 1304164 - Disable e10s for russian users through the system add-on
- bug 1301131 - Disable e10s for users who see long tab spinner
- bug 1297755 - Beta 50 A/B test will all multiprocessCompatible add-ons, except TabMixPlus
- bug 1302846 - Add Test Pilot add-ons to e10s whitelist