Electrolysis/Meetings/2016-05-26: Difference between revisions

cpeterson
(cpeterson)
 
(5 intermediate revisions by 3 users not shown)
Line 57: Line 57:
* p1 {{bug|1273685}} - PopupBlocking:UpdateBlockedPopups messages can be very large [wip]  
* p1 {{bug|1273685}} - PopupBlocking:UpdateBlockedPopups messages can be very large [wip]  
* Reviews
* Reviews
== mrbkap ==
* {{bug|1259517}} - dropping an image in a contenteditable element doesn't do anything - attached a patch, waiting for feedback.
* {{bug|1244533}} - dragend doesn't have coordinates - wrote a patch and checked it in.
* Other needinfos and reviews.


== gabor ==
== gabor ==
* landed all patches and requested uplifts focusing on sandboxing and multiple content processes
* landed all patches and requested uplifts focusing on sandboxing and multiple content processes
* (cannot join the meeting today, but happy to take bugs if they pop up)
* (cannot join the meeting today, but happy to take bugs if they pop up)
== chutten ==
* week 4 numbers are giving me trouble. Apparently we run out of space generating a derived stream for over three weeks worth of pings. The derived dataset is now just the fourth week (not everything from day 0 up to day 28), and analysis is running.


== haik ==
== haik ==
* {{bug|1274074}} console.log()ging too much data can crash e10s via IPC call from mozilla::dom::ProcessGlobal::SendAsyncMessage -- have a patch almost ready for review
* {{bug|1274074}} console.log()ging too much data can crash e10s via IPC call from mozilla::dom::ProcessGlobal::SendAsyncMessage -- have a patch almost ready for review
== aklotz ==
* {{bug|1263224}} Hand off a11y requests from RPC thread to main thread - Found out that QueryInterface wasn't working properly, had to rewrite a bunch of code to fix this. Blog post forthcoming to explain technical details.
* {{bug|1275731}} Add ia2marshal.dll to installer
* Still want to get a testable build out this week
== cpeterson ==
* [https://wiki.mozilla.org/Electrolysis/Release_Criteria#Slow_Scripts Slow Script release criterion] has been signed off. e10s does have a regression but Barbara and jimm have decided it is an acceptable regression:
** non-e10s = 854 hours between warnings (0.00117087669174 warnings per hour)
** e10s = 630 hours between warnings (0.00158655016424 warnings per hour)
* I am still pinging module and test owners about signing off tests disabled on e10s.
Confirmed users
3,314

edits