** Changed in: mir/0.8
Status: In Progress = Fix Committed
** Changed in: mir/0.8
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376324
Title:
This bug was fixed in the package mir - 0.8.2+15.04.20150115~rtm-
0ubuntu1
---
mir (0.8.2+15.04.20150115~rtm-0ubuntu1) 14.09; urgency=medium
[ Daniel van Vugt ]
* Bug fix release 0.8.2 (https://launchpad.net/mir/+milestone/0.8.2)
- ABIs all unchanged. No downstream projects
** Changed in: canonical-devices-system-image
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376324
Title:
/usr/sbin/unity-system-compositor:*** Error in
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity-system-compositor. This problem was most recently seen
with version 0.0.5+14.10.20140917-0ubuntu1, the problem page at
Suspicious still. There has been one similar (heap corruption?) crash on Mir
0.10.0 since it got released:
https://errors.ubuntu.com/oops/73fadb24-9ca5-11e4-a40f-fa163e78b027
Not sure what that is because we can't see the full stack trace without it
getting grouped under:
Adding canonical-devices-system-image in order to determine if we may add this
our rtm branches.
No one is complaining, but we are seeing this bug which has a solution, show up
in some crash logs.
Please target for an appropriate ww##.
** Also affects: canonical-devices-system-image
This could explain some reports, would definitely land it
** Changed in: canonical-devices-system-image
Importance: Undecided = High
** Changed in: canonical-devices-system-image
Status: New = Confirmed
** Changed in: canonical-devices-system-image
Milestone: None = ww05-2015
--
** Changed in: mir/0.8
Milestone: 0.8.1 = 0.8.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376324
Title:
/usr/sbin/unity-system-compositor:*** Error in `unity-system-
compositor': free():
I expect the fix is correct; we just haven't backported it to 0.8 yet.
** Changed in: mir/0.8
Status: Triaged = In Progress
** Changed in: mir/0.8
Assignee: (unassigned) = Daniel van Vugt (vanvugt)
** Branch linked: lp:~mir-team/mir/fix-1376324-0.8
--
You received this bug
This bug is still an issue. If you look at:
https://errors.ubuntu.com/problem/bfb855ebc60f251bf495a2ffb24f2924c50bdbf8
You will see Ubuntu Touch devices (including RTM) hitting this crash
every day.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: mir/0.8
Status: Triaged = In Progress
** Changed in: mir/0.8
Assignee: (unassigned) = Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376324
Sadly, not actually fixed yet. The same crash has occurred 52 times and
counting in vivid images that contain the fix (with Mir 0.9.0):
https://errors.ubuntu.com/problem/bfb855ebc60f251bf495a2ffb24f2924c50bdbf8
** Changed in: mir/0.8
Status: In Progress = Triaged
** Changed in: mir/0.8
Examples of vivid devices with Mir 0.9 that have reported this crash
recently:
https://errors.ubuntu.com/oops/8a0c78a0-99a3-11e4-be40-fa163e525ba7
https://errors.ubuntu.com/oops/9dae8c8a-9832-11e4-9b6e-fa163e75317b
https://errors.ubuntu.com/oops/529d3740-977a-11e4-9494-fa163e5bb1a2
--
You
BTW, errors.ubuntu.com's idea of StacktraceAddressSignature looks like
it could be subject to collisions. In the cases mentioned in comment
#13, they're only grouped together because they all have crashes that
are identical to depth 4:
#0 __libc_do_syscall () at
Oooh, we might be getting bug 1401488, which would have a similar
signature and could be accidentally grouped in here from Mir 0.9
devices.
** Changed in: mir
Milestone: 0.11.0 = 0.9.0
** Changed in: mir
Status: Triaged = Fix Released
** Changed in: mir (Ubuntu)
Status:
This bug was fixed in the package mir - 0.9.0+15.04.20141125-0ubuntu1
---
mir (0.9.0+15.04.20141125-0ubuntu1) vivid; urgency=medium
[ Alberto Aguirre ]
* New upstream release 0.9.0 (https://launchpad.net/mir/+milestone/0.9.0)
- Enhancements:
. New simpler API to
** Changed in: mir
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376324
Title:
/usr/sbin/unity-system-compositor:*** Error in `unity-system-
** Branch linked: lp:ubuntu/vivid-proposed/mir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376324
Title:
/usr/sbin/unity-system-compositor:*** Error in `unity-system-
compositor': free():
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.9.0
** Changed in: mir
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~vanvugt/mir/fix-1376324-more
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376324
Title:
/usr/sbin/unity-system-compositor:*** Error in `unity-system-
compositor': free():
** Also affects: mir/0.8
Importance: Undecided
Status: New
** Changed in: mir/0.8
Importance: Undecided = High
** Changed in: mir/0.8
Status: New = Triaged
** Changed in: mir/0.8
Milestone: None = 0.8.1
** Changed in: unity-system-compositor
Status: Incomplete =
** Changed in: mir
Milestone: 0.8.0 = 0.9.0
** Also affects: mir/0.8
Importance: High
Assignee: Alan Griffiths (alan-griffiths)
Status: In Progress
** No longer affects: mir
** No longer affects: mir/0.8
** Also affects: mir
Importance: Undecided
Status: New
**
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.8.0
** Changed in: mir
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Our experience clearly differs.
I find that it is often the second free of a block that triggers the
error. As the occasions when the free list has previously been corrupted
take disproportionately more time to solve I'm hoping this is an easy
one. ;)
--
You received this bug notification
It would depend entirely on how much the code touches the heap. In a
reasonably efficient project, the heap (structure not content) doesn't
change that much. You always have to assume malloc/free/new/delete are
slow and should avoid them. So the offending corruption could have
happened some time
** Branch linked: lp:~alan-griffiths/mir/fix-1376324
** Changed in: mir
Status: Incomplete = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376324
Title:
** Changed in: mir
Milestone: None = 0.8.0
** Changed in: mir (Ubuntu)
Status: Incomplete = Triaged
** Changed in: mir (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: unity-system-compositor
Importance: Undecided
Status: New
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mir
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
This looks as though the send_response_result member of
ProtobufResponder is no longer valid (i.e. that the ProtobufResponder at
this=0xac900574 has likely been freed).
I'm not sure what sequence of events would lead to a send_response()
message being passed to a no-longer valid ProtobufResponder
I've not been able to reproduce yet[1], but looking at the code I can't
see anything that prevents a buffer stream being owned by the compositor
(for composition) after the corresponding Surface and Session have been
closed. If that then attempts to complete a buffer swap then we would
see the
Crashing in free() like this means something else in the USC process has
corrupted the heap. And the effect is delayed, so you won't find the
root cause of the corruption in the stack traces. We'll have to do some
heap checking on live unity-system-compositor processes instead.
** Changed in: mir
Actually, no. There is a chance it's crashing where the error occurred,
but it's usually unlikely. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376324
Title:
32 matches
Mail list logo
