*** glibc detected *** double free or corruption (fasttop): 0x08214b48 ***

Bug #18682 reported by auspex
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Critical
Daniel Stone

Bug Description

Since latest dist-upgrade in breezy, starting KDM results in this "double free" error. I can override it
by setting the MALLOC_CHECK environment variable.

Revision history for this message
auspex (auspex) wrote :

*** Bug 18684 has been marked as a duplicate of this bug. ***

Revision history for this message
auspex (auspex) wrote :

Version: 4:3.4.1-0ubuntu4

Revision history for this message
Matthew Garrett (mjg59) wrote :

This actually seems to be an X issue. Derek, could you include lspci and
/var/log/Xorg.0.log output? Daniel, this seems to be hitting a lot of laptop
users, so it's probably of high priority.

Revision history for this message
Alex Roman (alex-roman) wrote :

This error seems to be related to the i810 driver for Xorg. It happens whenever
X gets started (X, startx, gdm).

If I change (in /etc/X11/xorg.conf) my driver from i810 to vesa, the problem
goes away. However, opengl acceleration is not supported by vesa. And we should
be using the i810 driver in Xorg.

I'll post my Xorg.0.log in a minute.

Revision history for this message
Alex Roman (alex-roman) wrote :

vesa driver also doesn't support my "native" resolution of 1280x800

Revision history for this message
Alex Roman (alex-roman) wrote :

Created an attachment (id=3286)
The Xorg configuration file

Revision history for this message
Alex Roman (alex-roman) wrote :

Created an attachment (id=3287)
Log for startx

Revision history for this message
Alex Roman (alex-roman) wrote :

Created an attachment (id=3288)
Xorg.0.log

Revision history for this message
Alex Roman (alex-roman) wrote :

I've attached my configuration file, the console output of startx, and the
Xorg.0.log file.

Using vesa also makes my display flicker slightly.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Slightly less than WORLD-ENDING severity

Revision history for this message
Alex Roman (alex-roman) wrote :

Any more updates on this bug? I am still clueless about how to fix it... or what
is causing it...

Revision history for this message
Daniel Stone (daniels) wrote :

i'm guessing that this occurs because of 855resolution running after your driver
has started. does making it run first help?

Revision history for this message
Alex Roman (alex-roman) wrote :

I'm not that familiar with the inner workings of the X server. What is
855resolution and how do I run it first?

Revision history for this message
Daniel Stone (daniels) wrote :

855resolution is a tool to educate your video BIOS about its native resolution

This bug has been marked as a duplicate of bug 9525.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.