FWIW, I can only reproduce this if either the resumed or the suspended app is a webapp (or the browser). Perhaps this is related to the fact that oxide runs in separate processes and we're sending sigstop/sigcont to a chain of processes?
FWIW, I can only reproduce this if either the resumed or the suspended app is a webapp (or the browser). Perhaps this is related to the fact that oxide runs in separate processes and we're sending sigstop/sigcont to a chain of processes?