During testing of Alacritty, it was observed that one could often provoke "resize glitches" when testing with Sway, where Alacritty would appear at 800x600 for what appeared to be a single frame, then resize to the appropriate size the next frame.

Running Alacritty under WAYLAND_DEBUG=1, one can observe the following behavior:

1. An xdg_surface is created, configured and acked, with no buffer yet available.
2. After initializing zwp_linux_dmabuf_v1, an 800x600 buffer is created, attached and committed.
3. A configure event is received for the xdg_surface, which results in:
   1. set_window_geometry is called with the new size
   2. A frame callback is registered
   3. A new buffer is created, with the old size (800x600)
   4. The buffer is attached and the surface is committed.
4. Then, on the next frame, a new buffer is created yet again, this time with the new size, which is attached and committed.

Even though we clearly acknowledge the changed size, and go through the effort of creating a new buffer, we spend time rendering an additional frame at the wrong resolution.

The issue exists with glutin_examples as well if one observes WAYLAND_DEBUG, but it does not cause the visible glitch.