Bug 99299

Summary: Constant crashes with Xorg killed by SIGABRT
Product: xorg Reporter: jonas <jonas>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
backtrace
none
var_log_messages (as collected by Fedora's gnome-abrt)
none
gdm-x-session log (should correspond to Xorg log) none

Description jonas@thiem.email 2017-01-06 12:13:07 UTC
I get constant crashes since a recent Xorg update, they happen almost daily, sometimes multiple times a day.

Details have also been captured here by the Fedora distribution: https://retrace.fedoraproject.org/faf/reports/1373071/

I also attached the backtrace as generated by gnome-abrt.
Comment 1 jonas@thiem.email 2017-01-06 12:14:46 UTC
Created attachment 128792 [details]
backtrace
Comment 2 jonas@thiem.email 2017-01-06 12:17:05 UTC
Created attachment 128793 [details]
var_log_messages (as collected by Fedora's gnome-abrt)
Comment 3 jonas@thiem.email 2017-01-06 13:00:22 UTC
Xorg version is X.Org X Server 1.19.0. I don't know how that maps to your higher numbered version scheme offered here on the bugtracker, so someone else feel free to enter the actual release that corresponds to.
Comment 4 Michel Dänzer 2017-01-07 06:52:59 UTC
Please attach the corresponding Xorg log file.
Comment 5 jonas@thiem.email 2017-01-07 20:10:51 UTC
For some reason gnome-abrt didn't collect it, and while I did try to find it at the time of the crash, it's not in /var/log/Xorg.0.log as it used to be historically and I had pretty bad internet so I couldn't really google the new location. Therefore I don't have it right now. I can gather it the next time this crash happens if that helps.
Comment 6 Alan Coopersmith 2017-01-07 20:18:02 UTC
Current releases of Fedora put the X log into the systemd journal instead of
/var/log/Xorg.0.log:
http://who-t.blogspot.com/2014/03/viewing-xorglog-with-journalctl.html
https://fedoraproject.org/wiki/How_to_debug_Xorg_problems

The backtrace suggests that glibc is aborting the server because it detected
an attempt to double free the same block of memory or similar memory corruption:

#3  0x00007efcf98a18ea in malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7efcf99acda8 "double free or corruption (!prev)", action=3) at malloc.c:5046
        buf = "0000000002cc5ed0"
        cp = <optimized out>
        ar_ptr = <optimized out>
        str = 0x7efcf99acda8 "double free or corruption (!prev)"
Comment 7 jonas@thiem.email 2017-01-13 11:33:06 UTC
Created attachment 128928 [details]
gdm-x-session log (should correspond to Xorg log)

It just crashed again. Attaching journalctl -b _COMM=gdm-x-session (which is supposedly the new Xorg log in Fedora) Crash happens around Jan 13 12:26:00 local time
Comment 8 Michel Dänzer 2017-01-18 07:47:48 UTC
Could be bug 99164.
Comment 9 jonasthiem 2017-01-18 13:47:05 UTC
If that helps anything, I set a custom keyboard combination ALT+D to open a new terminal (in the GNOME 3's gnome-control-center's keyboard shortcut settings).

The crash seems to preferably happen exactly when I press that keyboard combination - like every ~100th time. (I open a lot of new terminals during the day)
Comment 10 GitLab Migration User 2018-12-13 22:37:11 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/xserver/issues/514.

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.