Mir server crashes with "std::exception::what: Failed to get front buffer object" when trying to fullscreen a surface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Daniel van Vugt | ||
mir (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Mir server crashes with "std::exception
ERROR: /home/dan/
Dynamic exception type: N5boost16except
std::exception:
Mesa only has a fixed limit of (four?) front framebuffer objects available. So somehow the combination of fullscreen bypass and multimonitor is making us ask for more than that... (?)
Sorry I don't have a test case to reproduce it easily yet without using my own custom branch.
Related branches
- Kevin DuBois (community): Approve
- Cemil Azizoglu (community): Approve
- Alan Griffiths: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 106 lines (+38/-7)3 files modifiedsrc/platforms/mesa/display_buffer.cpp (+15/-6)
src/platforms/mesa/display_buffer.h (+1/-1)
tests/unit-tests/graphics/mesa/test_display_buffer.cpp (+22/-0)
- Cemil Azizoglu (community): Approve
- Alan Griffiths: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 127 lines (+49/-12)2 files modifiedsrc/platforms/mesa/display_buffer.cpp (+3/-8)
tests/unit-tests/graphics/mesa/test_display_buffer.cpp (+46/-4)
description: | updated |
tags: | added: fullscreen |
summary: |
Mir server crashes with "std::exception::what: Failed to get front - buffer object" when trying to fullscreen/bypass a surface in clone mode + buffer object" when trying to fullscreen a surface |
Changed in mir: | |
status: | Fix Committed → Fix Released |
I can't reproduce this now. But I'm sure someone will eventually.