We could dance around page flip scheduling and only do it when we think it's safe, but that's not a reliable solution and I suspect we already do that.
If we find there are still realistic ways of causing this error that are not themselves Mir bugs then we need to treat it as a warning only (one that does not repeat and flood the log).
We could dance around page flip scheduling and only do it when we think it's safe, but that's not a reliable solution and I suspect we already do that.
If we find there are still realistic ways of causing this error that are not themselves Mir bugs then we need to treat it as a warning only (one that does not repeat and flood the log).