Bug 94047 - *** Error in `/usr/lib/xorg/Xorg': free(): corrupted unsorted chunks: 0x000055d796f6c0c0 ***
Summary: *** Error in `/usr/lib/xorg/Xorg': free(): corrupted unsorted chunks: 0x0000...
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: highest blocker
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
Depends on:
Reported: 2016-02-08 14:29 UTC by Stanimir Stoyanov
Modified: 2019-11-27 13:42 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

GDB Backtrace (5.34 KB, text/plain)
2016-02-08 14:29 UTC, Stanimir Stoyanov
no flags Details
XOrg log (73.05 KB, text/plain)
2016-02-08 14:29 UTC, Stanimir Stoyanov
no flags Details
gdb backtrace 2 (5.93 KB, text/plain)
2016-02-09 04:39 UTC, Stanimir Stoyanov
no flags Details
Yet another slightly different backtrace (6.56 KB, text/plain)
2016-02-09 12:33 UTC, Stanimir Stoyanov
no flags Details

Description Stanimir Stoyanov 2016-02-08 14:29:20 UTC
Created attachment 121587 [details]
GDB Backtrace

The server crashes on debian unstable,
Package: xserver-xorg-core
Version: 2:1.18.0-3

related bug report there: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813716

I'm attaching the GDB backtrace and xorg log here as well.
Comment 1 Stanimir Stoyanov 2016-02-08 14:29:58 UTC
Created attachment 121588 [details]
XOrg log
Comment 2 Stanimir Stoyanov 2016-02-09 04:39:21 UTC
Created attachment 121610 [details]
gdb backtrace 2

Another crash, different gdb backtrace
Comment 3 Stanimir Stoyanov 2016-02-09 12:33:40 UTC
Created attachment 121616 [details]
Yet another slightly different backtrace
Comment 4 Stanimir Stoyanov 2016-02-22 16:38:31 UTC
Something is wrong with the current version in the Debian repos 2:2.99.917+git20160127-1+b1 - I switched back to 2:2.99.917-2~bpo8+1 version from the jessie-backports and could not reproduce a single crash since a whole week, compared to few times a day...

I hope it helps.
Comment 5 Chris Wilson 2016-02-22 21:18:18 UTC
The problem is those crashes are from victims and do not show the cause. You would have to run the Xserver under valgrind (and be sure to have the driver compiled with --enable-debug and/or --enable-valgrind).
Comment 6 Chris Wilson 2016-02-22 21:18:50 UTC
Alternatively, doing a (git) bisection on the driver may help.
Comment 7 Stanimir Stoyanov 2016-02-23 06:37:10 UTC
Thanks Chris! I've compiled the driver from the git repo with --enable-debug and --enable-valgrind, also installed valgrind on the machine. Waiting for the next crash with gdb attached.

Should I do anything valgrind specific other than the regular gdb backtrace retrieval?
Comment 8 Chris Wilson 2016-02-23 09:41:13 UTC
If it crashes again, then it is worth running under valgrind. You may have to do a couple of tricks, but if you can run

valgrind --log-file=/tmp/vg-xorg.txt Xorg -ac -noreset

then you can connect your normal Xsession (something like running gnome-session as your user should be enough). You should see both a message that xf86-video-intel is running under valgrind on both the stderr (Xorg.log) and the /tmp/vg-xorg.txt. If you don't see that message, check your --enable-valgrind compilation as otherwise the logs will be full of false positives.
Comment 9 Martin Peres 2019-11-27 13:42:13 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/86.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.