unity8/libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
kevin gunn | ||
Mir |
Fix Released
|
High
|
Kevin Dubois | ||
0.23 |
Fix Released
|
High
|
Kevin Dubois | ||
mir (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
xorg-server (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
Under heavy resizing (stress testing under Valgrind), my Mir client (Xmir) crashed with:
[1444895332.392862] <ERROR> MirBufferStreamAPI: Caught exception at client library boundary (in mir_buffer_
Dynamic exception type: boost::
std::exception:
The strange thing is it's only the client that died. The server survived and I can connect new clients to it.
---
Duplicate bug reports now show Unity8 is another such client suffering from this crash. It's occurring on phones and desktops in the wild.
tags: | added: xmir |
summary: |
- Mir client died with "std::exception::what: disconnected: no new - buffers" via ExchangeSemantics::submit() + libmirclient gives up and exits prematurely with "std::exception::what: + disconnected: no new buffers" via ExchangeSemantics::submit() |
Changed in mir (Ubuntu): | |
importance: | Undecided → High |
Changed in xorg-server (Ubuntu): | |
importance: | Undecided → High |
Changed in xorg-server (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in mir: | |
importance: | High → Critical |
Changed in mir (Ubuntu): | |
importance: | High → Critical |
Changed in mir: | |
status: | New → Confirmed |
description: | updated |
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → kevin gunn (kgunn72) |
milestone: | none → ww04-2016 |
summary: |
- libmirclient gives up and exits prematurely with "std::exception::what: - disconnected: no new buffers" via ExchangeSemantics::submit() + libmirclient gives up and terminates prematurely with + "std::exception::what: disconnected: no new buffers" via + ExchangeSemantics::submit() |
Changed in canonical-devices-system-image: | |
milestone: | ww04-2016 → ww08-2016 |
Changed in canonical-devices-system-image: | |
importance: | Critical → High |
Changed in canonical-devices-system-image: | |
milestone: | ww08-2016 → 11 |
Changed in canonical-devices-system-image: | |
milestone: | 11 → backlog |
Changed in mir: | |
milestone: | 0.24.0 → 0.25.0 |
Changed in mir: | |
milestone: | 0.25.0 → none |
description: | updated |
Changed in mir (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in canonical-devices-system-image: | |
status: | Confirmed → Fix Committed |
Changed in mir: | |
status: | Fix Committed → Fix Released |
Changed in canonical-devices-system-image: | |
milestone: | backlog → 13 |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
BTW, Valgrind found no errors in the client before the crash.