[Bug 328035] Re: X server crash: *** glibc detected *** free(): in valid next size (fast)

2009-03-24 Thread Matt Zimmerman
I just realized a new element that all of these scenarios have in common: the screensaver. The screensaver is activated when coming back from resume. The crash during installation happened at just about the point where the screensaver activated due to an activity timeout (I noticed during my

[Bug 328035] Re: X server crash: *** glibc detected *** free(): in valid next size (fast)

2009-03-24 Thread Chris Jones
Matt: if it is screensaver related, it's probably not because of some 3D parts - I have a blank screen and am seeing this, although I've yet to find a log of it (perhaps just because of a lack of retention of Xorg logs for very long, which is something I filed separately a while ago as Bug

[Bug 328035] Re: X server crash: *** glibc detected *** free(): in valid next size (fast)

2009-03-24 Thread Robert Jordens
I get this crash on resume from time to time. But I also get a crash with the same symptoms on switching between the internal LVDS and an external VGA with xrandr but without a suspend/resume. -- X server crash: *** glibc detected *** free(): in valid next size (fast)

[Bug 328035] Re: X server crash: *** glibc detected *** free(): in valid next size (fast)

2009-03-24 Thread Tormod Volden
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