Bug 58834

Summary: Crash in i915_set_vertex_buffers with kwin
Product: Mesa Reporter: dflogeras2
Component: Drivers/Gallium/i915gAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: kamil.lech.roman
Version: 9.0   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Backtrace of crash

Description dflogeras2 2012-12-28 18:30:34 UTC 
Gentoo (amd64) using:

kde-4.9.3
xorg-server-1.13.0 (tried 1.13.1 as well)
mesa-9.0 (tried 9.0.1 as well)
xf86-video-intel-2.20.13 (tried 2.20.16 as well)

hardware is:
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10)

If I enable the "cover switch" or "flip swith" effects for alt-tab, I will very often get a crash with alt-tab which ends in the i915_set_vertex_buffers function (line 1000 of gallium/drivers/i915/i915_state.c), trying to dereference a 0x0 buffer.

The buffers[0] data structure contains just null pointers, and a stride value of 8, and line 1000 tries to dereference one of them.  This may be the cause or the effect, that's not for me to judge :)

See attached backtrace.  Turning off unredirect fullscreen windows did not affect it (there were some related bugs a year or two ago)
Comment 1 dflogeras2 2012-12-28 18:31:08 UTC 
Created attachment 72225 [details] [review]
Backtrace of crash
Comment 2 Kenneth Graunke 2012-12-29 22:48:41 UTC 
This is an i915g bug, which isn't supported by us...changing the component.
Comment 3 GitLab Migration User 2019-09-18 19:30:49 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/mesa/mesa/issues/662.

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.