Comment 3 for bug 1659298

Oh, actually, ignore^, I don't think sync would be lost. The issue occurs when trying to set the swapinterval twice with the same value.

The side effect is that the driver would get an error RC for issuing the set_swapinterval hook (-1 on android, MIR_MESA_FALSE for mesa). I think most sensible drivers would ignore this error, but that relies on the drivers being sensible.