I got suspicious when I saw LogVMessageVerb in the backtrace, which I have touched recently myself... Sure enough I did not think about the possibility of clocks going backwards (which they sometimes do after resume) when I worked on the timestamp stuff and you end up with nice timestamps (like below) with no bounds checking. The tmpBuf is overflowed and free()'ing it messes up. Sorry.
[-1009303149.602078] (II) AIGLX: Suspending AIGLX clients for VT switch The timestamp patch was supposed to be taken away before Beta anyway. Bryce, can you please remove it now, and I will fix the timestamp again for later. -- X server crash: *** glibc detected *** free(): in valid next size (fast) https://bugs.launchpad.net/bugs/328035 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs
