<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - segfault at 234 error 4 in i915_dri.so"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100189#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - segfault at 234 error 4 in i915_dri.so"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100189">bug 100189</a>
from <span class="vcard"><a class="email" href="mailto:javibato@hotmail.com" title="Javi Ballester Tomás <javibato@hotmail.com>"> <span class="fn">Javi Ballester Tomás</span></a>
</span></b>
<pre>The result of 'git bisect':
e027935a795ecf546f3e4abcc25655766f9615ac is the first bad commit
commit e027935a795ecf546f3e4abcc25655766f9615ac
Author: Marek Olšák <<a href="mailto:marek.olsak@amd.com">marek.olsak@amd.com</a>>
Date: Wed Feb 22 19:59:27 2017 +0100
st/mesa: don't update unrelated states in non-draw calls such as Clear
If a VAO isn't bound and u_vbuf isn't enabled because of the Core profile,
we'll get user vertex buffers in drivers if we update vertex buffers
in glClear. So don't do that.
This fixes a regression since disabling u_vbuf for Core profiles.
Reviewed-by: Brian Paul <<a href="mailto:brianp@vmware.com">brianp@vmware.com</a>>
:040000 040000 7843bc274cb97b72ebd0ba00906ba3baeecf0658
97a362bcd14da53ec9cfa940b3612d77e54be72d M src</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>