When stressed by a load of clients starting at once: Failed to get PRIME fd from gbm bo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Alan Griffiths | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I initially found this with miral-shell, but found similar behaviour with mir_demo_
Start a shell, then start all the mir_demo_client_XXX apps. (For convenience see attached script.)
Then start closing apps one by one: At some point the server dies with a segfault.
With a bit of debugging I managed to catch the following error just before the segfault:
ERROR: /home/alan/
Dynamic exception type: boost::
std::exception:
Related branches
- Chris Halse Rogers: Approve
- Mir CI Bot: Approve (continuous-integration)
- Andreas Pokorny (community): Approve
- Cemil Azizoglu (community): Approve
-
Diff: 156 lines (+70/-61)1 file modifiedsrc/renderers/gl/renderer.cpp (+70/-61)
tags: | added: mesa-x11 |
Changed in mir: | |
importance: | Medium → High |
Changed in mir: | |
status: | New → In Progress |
assignee: | nobody → Alan Griffiths (alan-griffiths) |
milestone: | none → 0.25.0 |
Changed in mir: | |
status: | Fix Committed → Fix Released |
A bit more investigation suggests this is only happening with mir-on-X11. Maybe something there is a bit racy.