Electrolysis/Meetings/2016-04-21: Difference between revisions

Jump to navigation Jump to search
gabor's progress
(adding chutten)
(gabor's progress)
Line 73: Line 73:
** made a patch to try out 1mb dirty pages limitation, then the diff on page-cache and heap-unclassified are similar, am tring to comapre the talos' scores
** made a patch to try out 1mb dirty pages limitation, then the diff on page-cache and heap-unclassified are similar, am tring to comapre the talos' scores
** jemalloc4 regresses talos, ni'd erahm and glandium for whether to land bug 1005844 at first
** jemalloc4 regresses talos, ni'd erahm and glandium for whether to land bug 1005844 at first
== gabor ==
* {{bug|1247420}} - (m9 1255138 - Resizing windows from JS is not supported in e10s mode) - I'm struggling with the test. The individual features are complete but the test is quite broken and hard to get right for both e10s and non-e10s to work. If something goes wrong with it (typically only on try) because of a tricky coordinate math random things happen and it's hard to track what went wrong exactly. I'm considering to just rewrite the entire test from scratch, I wasted too much time on it already. Another issue that this is a quite tricky patch, since layout is not particular straightforward when it comes to window manipulation to say the least... and splitting the whole thing in to process did not help. I need someone who can review it and I'm concerned about the uplift a bit.
* {{bug|1263953}} - (Reduce the growth rate of Pickle) - Landed.
* {{bug|1264383}} - (Add-on multiprocess compatible shims stops TabSelect event listeners being removed from the tab container) - requested uplift, we decided not to uplift to beta/esr.
* {{bug|1262661}} - (Many large SessionStore:update messages) - One thing we should do is breaking up big messages automatically, but maybe the recent work on pickle will be enough. Another thing is that a, we always send the whole session store instead of the changes only b, we have a MessageQueue that sends the messages in batches. We could be smarter there too by forcing the queue to fire up a message before the timeout beyond a certain size.
* more addon reviews...

Navigation menu