Electrolysis/Meetings/2015-12-03
< Electrolysis | Meetings
Jump to navigation
Jump to search
« previous week | index | next week »
mconley
- M8 bug 1177310 - [e10s] Stop using CPOWs on application shutdown
- Final reviews are in, and has landed on fx-team.
- Hoping I can get some QA eyes on this, since we don't have an amazing test story for full browser restart (yet - see bug 1228120). Either manually banging on it, or helping me keep an eye on Bugzilla and the support channels about any lost sessions or crashes on shutdown.
- M8 bug 1159827 - [e10s] We always show the spinner when closing a tab
- Unable to reproduce this. Blocked waiting on STR.
- M8 bug 1227312 - Investigate: many more content process crashes than aborts should not be possible.
- Reasonably certain I found cause - we were double-counting the number of crash reports we were gathering (details). Handed off to jimm because it's touchy code that he's familiar with.
- Perf P1 bug 1193838 - Make it possible to gather profiles from processes that have exited
- This landed on inbound today
- Perf P1 bug 1195295 - content-sessionStore.js sends a sync message to the parent in SyncHandler.init
- Patch written and reviewed. Waiting on bug 1177310 to land and stick.
- Perf P1 bug 1221846 - Get Task Tracer working on desktop
- Almost got this building - just dealing with a linker error.
- I've got local modifications in the Gecko Profiler add-on to let us toggle this feature.
- Talked to cervantes in #perf, and we're going to have a chat in Orlando - seems that the UI for interpreting Task Tracer logs isn't amazing for analysis, and they want to try building it into Cleopatra instead.
- bug 1225921 - Async tab and window flushing may make it possible to accidentally save tabs we want to forget
- Tests and potential patch written. Waiting on review feedback.
- bug 1226333 - Add tests for async window flushing
- Been doing lots of try pushes to get the intermittents figured out. Seems to be related to the increasing ID that we send from the child so that the parent doesn't accidentally overwrite synchronously flushed data with asynchronously flushed data... interestingly, the intermittents go away with bug 1195295 landed, but I'd still like to understand why this is happening.