Okay, so the problem was that the texture cache was using an "invalid ID" to do some of its tracking, and the new IntWrapper-based BufferId doesn't have the concept of an invalid id.
The previous invalid id was "0", so this would only affect the first buffer allocated on the system. On the android platform, the first buffer allocated is typically the framebuffers (which dont get involved with the texture cache), so thats why I could not reproduce with the demo shells on android. qtmir doesn't use this code, so it wouldn't be affected either. I could reproduce on mesa, and it would seem to affect only the 1st buffer of the 1st client. Working on fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1362444 Title: [regression] First frame is composited as black (even though the client has provided a non-black frame) Status in Mir: Triaged Status in Mir 0.7 series: In Progress Status in “mir” package in Ubuntu: New Bug description: [regression] First frame is composited as black (even though the client has provided a non-black frame). Test case A: 1. Run mir_demo_client_fingerpaint Expected: The canvas coloured window to appear. Observed: A black window appears. The canvas only appears after you start painting. Test case B: 1. Insert a sleep into the start of mir_demo_client_progressbar Expected: After the sleep, the first composited frame has a blue background. Observed: After the sleep, the first composited frame is all black. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1362444/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
