Summary: | Xorg Segfaults when certain X apps (Gtk ones?) are invoked | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Tom Crane <TPCbz> | ||||
Component: | Driver/mach64 | Assignee: | Xorg Project Team <xorg-team> | ||||
Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | blocker | ||||||
Priority: | medium | CC: | TPCbz | ||||
Version: | 7.7 (2012.06) | ||||||
Hardware: | x86 (IA32) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Tom Crane
2013-10-17 00:55:51 UTC
I have discovered that enabling the xorg.conf option "ExaNoComposite" as noted at https://wiki.archlinux.org/index.php/mach64 provides a workaround and avoids the segfault triggered previously by X apps such as the Gimp. Tom Crane Some further investigation with gdb: The problems at xf86-video-mach64-6.9.4/src/atimach64render.c, Mach64CheckTexture(PicturePtr pPict) { int w = pPict->pDrawable->width; occurs when pPict->pDrawable == NULL, the final pointer dereference pPict->pDrawable->width then causes the segfault. I found the patch at http://lists.x.org/archives/xorg-devel/2013-June/036430.html is a workaround and allows the xorg.conf ExaNoComposite option to be turned off and my brief initial tests gave much improved accelerated graphics performance and no more segfaults. Could I request the patch be incorporated into the next release? Thanks Tom Crane. That patch has already been pushed to git master for the next release: http://cgit.freedesktop.org/xorg/driver/xf86-video-mach64/commit/?id=2c83b465b336a012f2d2716940bf483358388000 -- 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-mach64/issues/1. |
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.