Electrolysis/Meetings/2016-02-18: Difference between revisions

gabor's progress edit
(gabor's progress)
(gabor's progress edit)
Line 34: Line 34:


== gabor ==
== gabor ==
* {{bug|1179735}} (p1 perf, - tp5o_scroll regression) - Did some profiling locally on the original tests after applying Mike's patches. Had a bunch of theories but neither of them turned out to be
* {{bug|1179735}} (p1 perf, - tp5o_scroll regression) - Did some profiling locally on the original tests after applying Mike's patches. Had a bunch of theories but neither of them turned out to be true (vsync on compositor side, slower js in e10s, something holding up the ticks, etc.). At this point it just seems that we paint slower for some reason... but nothing obvious can be spotted on the profiler data. Unfortunately the test does seem quite valid and the perf regression is quite significant.
true (vsync on compositor side, slower js in e10s, something holding up the ticks, etc.). At this
point it just seems that we paint slower for some reason... but nothing obvious can be spotted
on the profiler data. Unfortunately the test does seem quite valid and the perf regression is quite
significant.
* {{bug|1232638}} - (p1 perf, -IPDL::PCookieService::RecvGetCookieString causing janks) - As it turns out it should be possible to get rid of the cookie getters in the child for the http requests. I could not find this to be a perf problem for page loads, so I'm still unsure about its priority.
* {{bug|1232638}} - (p1 perf, -IPDL::PCookieService::RecvGetCookieString causing janks) - As it turns out it should be possible to get rid of the cookie getters in the child for the http requests. I could not find this to be a perf problem for page loads, so I'm still unsure about its priority.
* {{bug|1248130}} - (m9, Crashing user in wrong e10s experiment branch) - Tried some edge cases to reproduce it. I found some cases where the flag is not correct temporarily (after disabling an addon the flag is updated but the status of the addon is only updated after restart, same for enabling)
* {{bug|1248130}} - (m9, Crashing user in wrong e10s experiment branch) - Tried some edge cases to reproduce it. I found some cases where the flag is not correct temporarily (after disabling an addon the flag is updated but the status of the addon is only updated after restart, same for enabling)