18:00:58 #startmeeting tor browser 18:00:58 Meeting started Mon Jun 13 18:00:58 2016 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:58 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:01:10 hi everyone to another weekly tor browser meeting 18:01:17 hi 18:01:26 hi 18:01:41 Is debian ok? I can test it now (a meeting? okay I'll stop talking now) 18:02:11 hi all 18:02:22 Sam_: you are welcome. if you problems persist then filing a bug at trac,torproject.org might help 18:02:37 we can investigate that there then 18:02:46 who wants to go first today? 18:02:47 Thanks. 18:03:46 * mcs will go first 18:03:52 Last week, Kathy and helped with triage of new Tor Browser bugs, e.g., #19269. 18:03:59 We helped with some updater “fallout”, e.g., #19348. 18:04:19 We also worked on #19273 (a SponsorU task) but do not have a patch yet. 18:04:32 Then we spent a lot of time trying to reproduce and debug an issue that GeKo has observed while running an ASan build (no ticket for this one yet). 18:04:43 This week we will get back to #19273 and, time permitting, work on assorted loose ends such as #17858, #18330, and #18913. 18:04:49 That’s all for now. 18:05:56 * GeKo i can go next 18:06:29 the past week was a bit frustrating. a lot of energy went into non-Tor Browser things 18:06:55 then I dealt with Tor Browser 6.x fallout and tried to enumerate the 6.0 issues 18:07:15 the most pressing thing currently is #19400 18:07:29 which i spent a lot of time trying to reproduce but i failed 18:07:54 there is a probably related crash on mega.nz (see the blog comments even for links that should crash) 18:08:07 but that one as well is not reproducible on any of my machines 18:08:27 i spent a bit time on #19401 18:08:55 and stared to make a list for #19274 to scope the work there 18:09:35 this week i plan to work further on #19274 and related tasks and we might need to get a fixup release out for #19400 and friends 18:09:55 might be smart to fix the xrender bug for linux users in it as well 18:10:17 if there is still time left i plan to resume work on the design doc update. 18:10:20 that's it for me. 18:11:26 * arthuredelstein can go 18:11:35 This past week, I worked on regression tests for #16998, 18:11:41 I reviewed #19401, 18:11:48 I started trying out libm replacements for #13018, 18:11:53 (I currently like https://github.com/JuliaLang/openlibm) 18:12:11 I did some reading to try to understand #10281, 18:12:24 and I nearly finished a new patch for upstreaming our font whitelisting feature: https://bugzilla.mozilla.org/show_bug.cgi?id=1121643 18:12:58 This week I want to continue on #13018/#13017, look more at #10281, and maybe work on more patches for upstreaming 18:13:06 That's it for me 18:15:28 * boklm can go 18:15:43 This past week I helped get the releases out. I made a patch for #19348 and started one for #18497. 18:15:53 This week I'm planning to work on #19402, #18497, #15138, #19067, #15994, and start looking at the release signing process 18:16:01 Maybe also #18923 to use it in #15994 18:16:10 That's it for me 18:16:32 wow, a bunch of stuff :) 18:17:57 can i pipe up a second? sorry to interrupt, but i have a tor browser dev-relevant question 18:18:04 sure 18:18:23 is there any interest in this patch that turns on W^X in the js jit? 18:18:26 http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/ports/www/firefox-esr/patches/patch-js_src_jit_ExecutableAllocator_cpp?rev=1.1&content-type=text/plain 18:18:48 firefox-esr and firefox have that on openbsd-current for a little bit now 18:19:14 that's what we are currently testing in the 6.5alpha series i think 18:19:17 tor browser under openbsd will have it, i feel like it should be upstream'd 18:19:27 ah, cool. i was looking at the wrong branch then to figure out if you had it or not 18:19:30 sorry for the noise 18:19:33 * attila pipes down 18:19:40 #12523 18:20:06 super cool 18:20:51 anyone else here for a status update? 18:21:48 okay, let's move to the dicussion part 18:21:58 i have only one point: #19400 18:22:07 I will speak briefly to say that amoghbl1 who can't make it today, has made progress on ESR45/6.5 based Orfox work. Everything is building. I am reviewing code this week, and we'll have to see what new android/java network code and features have been added next. 18:22:12 that's all. 18:22:37 cool, there is stuff with tbb-mobile tagged that mike found during the network audit 18:22:47 was just looking those up 18:22:49 thx 18:23:35 re #19400: we need to find out asap what is going on i think. 18:24:14 mcs: arthuredelstein: if you could look at trying to reproduce that problem that would be super helpful 18:24:28 will do. I already tried via facebook but couldn't reproduce it. 18:24:52 as i said there is a probably related crash on mega.nz (see comments for hints) 18:25:05 GeKo: We will take a look also. 18:25:14 thanks. 18:25:30 i somehow doubt one of our crash fixups is causing this 18:25:51 but on the other hand i doubt mozilla introduced that without no user complaining 18:26:00 so, dunno 18:26:09 I wonder if it's related to our previous mega crash problem 18:26:38 hrm. might be an interesting thought 18:27:13 if you don't find out what is going on my plan is to try getting random people hitting the crash testing some custom builds i make 18:27:26 we'll see how fast we can get to the bottom of this. 18:27:45 apart from that there is nothing on my list 18:27:50 (for discussion) 18:28:04 does anybody have something else? 18:29:25 Nothing from me. 18:30:01 nor me 18:30:13 okay, thanks for the short meeting then *baf* 18:30:23 #endmeeting