It's crashing in an innocent "new" call, which means the heap corruption
has occurred at some unknown location in the past :(
#8 0xb697808c in operator new (sz=sz@entry=1264) at
../../../../src/libstdc++-v3/libsupc++/new_op.cc:49
p = <optimized out>
#9 0xb6b0733e in android::InputDispatcher::notifyMotion (this=0x1ed8800,
args=0xabbfe428) at
/build/buildd/mir-0.9.0+15.04.20141125/3rd_party/android-input/android/frameworks/base/services/input/InputDispatcher.cpp:2410
newEntry = <optimized out>
policyFlags = 1174405120
needWake = <optimized out>
We'll need to reproduce the crash under valgrind (or env
MALLOC_CHECK_=3) to get a better core dump that shows the source of the
problem.
** Changed in: mir (Ubuntu)
Status: New => Incomplete
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401488
Title:
unity-system-compositor assert failure: *** Error in `unity-system-
compositor': corrupted double-linked list: 0xaa817808 ***
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1401488/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
