Dropped priority. Now we understand this problem, it's just going to be a series of workarounds in Mir, and Chris suggested another good one in the hangout today that might also fix it for radeon and nouveau (bug 1211700). Plus we have some workarounds proven already in comment #20.
Long term we need a proper fix in the driver, so it's a Mesa bug. A solution in theory already exists: https://www.usenix.org/legacy/event/atc11/tech/final_files/Kato.pdf ** Changed in: mir/0.26 Milestone: 0.26.2 => None ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1665802 Title: [regression] mir_demo_client_eglplasma results in 100% cpu and hardly any updates in dragonboard Status in Mir: In Progress Status in Mir 0.26 series: Triaged Status in mesa package in Ubuntu: New Bug description: On a dragonboard 410c, With Mir 0.25 mir_demo_client_eglplasma renders steadily at 15FPS and with low cpu usage. With mir 0.26.1, the process takes 100% cpu (according to top) and frames hardly update on screen, but the client performance is 60-27FPS. To replicate: mir_demo_server --arw-file --launch-client mir_demo_client_eglplasma To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1665802/+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
