[regression] Mir servers crash with SIGABRT - assertion failed at buffer_queue.cpp:136 - "!pending_client_notifications.empty()"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Critical
|
Alexandros Frantzis | ||
0.4 |
Won't Fix
|
Critical
|
Unassigned | ||
0.5 |
Fix Released
|
Critical
|
Mir development team | ||
mir (Ubuntu) |
Fix Released
|
Critical
|
Mir development team | ||
unity-system-compositor (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Can't say so much, opened the launched an had a crash.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-system-
ProcVersionSign
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.3-0ubuntu2
Architecture: amd64
BootLog:
* Setting up X socket directories... [160G
[154G[ OK ]
* Starting automatic crash report generation: apport [160G
[154G[ OK ]
Date: Sat Jun 28 20:23:03 2014
ExecutablePath: /usr/sbin/
GraphicsCard:
Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:0136]
Subsystem: Acer Incorporated [ALI] Device [1025:0136]
InstallationDate: Installed on 2014-06-19 (9 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64+mac (20140619)
ProcCmdline: /usr/sbin/
ProcEnviron:
Signal: 6
SourcePackage: unity-system-
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
Title: unity-system-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
version.libdrm: libdrm2 2.4.54-1
version.lightdm: lightdm 1.11.3-0ubuntu1
version.mesa: libegl1-mesa-dev N/A
Related branches
- Daniel van Vugt: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Alan Griffiths: Approve
-
Diff: 25 lines (+14/-1)1 file modifiedsrc/server/compositor/buffer_queue.cpp (+14/-1)
- Kevin DuBois (community): Approve
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Cemil Azizoglu (community): Approve
-
Diff: 25 lines (+14/-1)1 file modifiedsrc/server/compositor/buffer_queue.cpp (+14/-1)
summary: |
- unity-system-compositor crashed with SIGABRT in __assert_fail_base() + unity-system-compositor crashed with SIGABRT - assertion failed at + buffer_queue.cpp:136 - "!pending_client_notifications.empty()" |
Changed in mir: | |
importance: | Undecided → Critical |
Changed in unity-system-compositor (Ubuntu): | |
importance: | Medium → Critical |
information type: | Private → Public |
information type: | Public → Public Security |
information type: | Public Security → Public |
tags: | added: rtm14 |
Changed in mir: | |
milestone: | none → 0.5.0 |
Changed in mir: | |
status: | New → Triaged |
affects: | unity-system-compositor (Ubuntu) → mir (Ubuntu) |
Changed in mir (Ubuntu): | |
status: | New → Triaged |
Changed in unity-system-compositor (Ubuntu): | |
status: | New → Invalid |
Changed in mir: | |
milestone: | 0.5.0 → 0.6.0 |
Changed in mir: | |
status: | Triaged → In Progress |
summary: |
- unity-system-compositor crashed with SIGABRT - assertion failed at + Mir servers crash with SIGABRT - assertion failed at buffer_queue.cpp:136 - "!pending_client_notifications.empty()" |
Changed in mir (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Mir development team (mir-team) |
Changed in mir: | |
status: | Fix Committed → Fix Released |
This seems related to https:/ /code.launchpad .net/~mir- team/mir/ fix-1339700/ +merge/ 226233 , so it may be a different manifestation of bug 1339700.
From Alberto's last comment in the MP above:
"Ok, after staring at TimeoutFrameDro ppingPolicy there are scenarios that can lead to an assert." (referring to the assertion we are seeing in this bug)