On Fri, Jun 19, 2015 at 12:45 PM, Patrick Walton
wrote:
> It's fine to pass channels over channels as long as those channels don't
> cross process boundaries.
>
Out of interest, why can't you pass channels over channels across a process
boundary?
Rob
--
oIo otoeololo oyooouo otohoaoto oaonoyoo
For the memory profiler, it seems like some socket abstraction would
work fine. The master process can just listen on a IPC socket and the
messages can get broadcast to it.
jack.
On Thu, Jun 18, 2015 at 6:50 PM, Nicholas Nethercote
wrote:
> On Thu, Jun 18, 2015 at 5:45 PM, Patrick Walton wrote:
On Thu, Jun 18, 2015 at 5:45 PM, Patrick Walton wrote:
> It's fine to pass channels over channels as long as those channels don't
> cross process boundaries. In that case, the paint task lives in the chrome
> process (since it has access to the GPU), so you're fine. The problematic
> cases are ess
It's fine to pass channels over channels as long as those channels don't
cross process boundaries. In that case, the paint task lives in the chrome
process (since it has access to the GPU), so you're fine. The problematic
cases are essentially {script,layout} <-> (anything else).
Patrick
_
The memory profiler relies heavily on passing channels over channels.
The memory profiler makes measurement requests of threads and passes
them a channel through which they can return the measurements.
One example from paint_task.rs:
impl Reporter for PaintChan {
// Just injects an appropriat
Hi everyone,
I'm rebasing my multiprocess patch and found that many of the new features
that have landed were implemented in a way that was incompatible with
multiprocess Servo. In particular:
* WebDriver passes channels over channels between script and the chrome
process.
* Canvas relies on pas
6 matches
Mail list logo
