On 10.06.2014 18:54, Michael Terry wrote:
> OK, got it in a state and tested via "ps aux" whether it was actually
> SIGSTOPped and seems like no. So I'm guessing some sort of render
> block... non-blocking mode was supposed to fix that, but perhaps in
> conjunction with Mir lifecycles, something still blocks inactive
> sessions.It only
It only...?
In any case, I'm not aware of anything that could be dubbed "Mir
lifecycles"... Blocked rendering would be the only thing I could explain
this with.
On 10.06.2014 18:54, Michael Terry wrote:
> OK, got it in a state and tested via "ps aux" whether it was actually
> SIGSTOPped and seems like no. So I'm guessing some sort of render
> block... non-blocking mode was supposed to fix that, but perhaps in
> conjunction with Mir lifecycles, something still blocks inactive
> sessions.It only
It only...?
In any case, I'm not aware of anything that could be dubbed "Mir
lifecycles"... Blocked rendering would be the only thing I could explain
this with.