Hi Daniel, Regarding #1, I instrumented our DRM driver and compared the debug output between Xorg and Wayland login screen, since the same symptom occurs there.
For Xorg (on Ubuntu 16.04), by the time the login screen shows up, I only see one request for a FB. For Wayland (on Ubuntu 17.10), when the login screen tries to come up I see the following sequence: FB 1 (prepare_fb) FB 2 (prepare_fb) FB 1 (cleanup_fb) FB 3 (prepare_fb) FB 2 (cleanup_fb) Now FB 1 and 2 are freed and the login screen presumably is displayed on FB 3. prepare_fb is where the surface gets pinned, and cleanup_fb is where it gets unpinned. So at one point in this sequence, the user mode is attempting to have 2 surfaces pinned. I'm guessing it doesn't want to give up the first FB until it knows the 2nd one is available. I can work around this one on my end, but I'd like to confirm that this behavior is from the user mode. It is possible that I goofed on my end, so I wanted to be sure. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1722897 Title: Ubuntu Wayland seems to be allocating 2-3 framebuffer sized surfaces (more than Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1722897/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
