After a discussion with :mcmanus regarding Bug 1259508, it seems that this should be remoted anyways, regardless of the sandboxing issue. See Bug 1259508 Comment 16, for further information.
:bagder, I was told that you are probably the right person to work on this. I don't know how much work is required and how busy you are. This is currently one of the last bugs blocking us from enabling seccomp on nightly. If you are too busy to work on this, I would write a workaround patch for Bug 1259508 which can then be backed out again once this bug is resolved.
Component: General → Networking: HTTP
Product: Firefox → Core
Assignee: nobody → daniel
tracking-e10s: --- → ?
Whiteboard: sblc1 → sblc1 [necko-active]
I'm moving this up to the top of my list. Just these national holidays (Sweden) in the way...
Great thanks Daniel.
Created attachment 8750252 [details] [diff] [review] 0001-Bug-1270147-remote-the-SpeculativeConnect-call-r-mcm.patch Were you thinking about something as simple as this? I'm not sure exactly how I should proceed to test this specifically. Any suggestions? (I'll send it off on a try-run of course.)
Attachment #8750252 - Flags: review?(mcmanus)
Attachment #8750252 - Flags: review?(mcmanus) → review+
to test this I think its sufficient to put print/log in the new code as well as the parent execution of the remoted call.. and then try and trigger it based on the stack in https://bug1259508.bmoattachments.org/attachment.cgi?id=8735522
This is the try-run: https://treeherder.mozilla.org/#/jobs?repo=try&revision=8b1b092b5cf9
Wow, it wasn't that easy to actually trigger that code path but I've now tested it manually and the above try-run seems to agree. Good to merge methinks.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox49: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
You need to log in before you can comment on or make changes to this bug.