Re: Changing our thread APIs for Quantum DOM scheduling

2017-05-19 Thread Chris Peterson
The Quantum DOM doc says only content processes will get cooperative threading. How will cooperative threading work with multiple content processes (e10s-multi)? Will there be inter-process scheduling? For example, if content process #1 has one or more foreground tabs (from multiple windows) an

Re: Changing our thread APIs for Quantum DOM scheduling

2017-05-19 Thread David Teller
Out of curiosity, how will this interact with nsCOMPtr thread-safe (or thread-unsafe) refcounting? Also, in code I have seen, `NS_IsMainThread` is used mainly for assertion checking. I *think* that the semantics you detail below will work, but do you know if there is a way to make sure of that? A

Changing our thread APIs for Quantum DOM scheduling

2017-05-18 Thread Bill McCloskey
Hi everyone, One of the challenges of the Quantum DOM project is that we will soon have multiple "main" threads [1]. These will be real OS threads, but only one of them will be allowed to run code at any given time. We will switch between them at well-defined points (currently just the JS interrup