From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 97059] Tahiti+DRI3+Unity+Blender corruption
Date: Tue, 26 Jul 2016 04:00:08 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1063886663=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 68F366E416
for ; Tue, 26 Jul 2016 04:00:08 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1063886663==
Content-Type: multipart/alternative; boundary="14695056080.8dD4.29921";
charset="UTF-8"
--14695056080.8dD4.29921
Date: Tue, 26 Jul 2016 04:00:07 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D97059
--- Comment #8 from Michel D=C3=A4nzer ---
I suspect this is a blender bug. It clearly doesn't render at all to the
corrupted parts of its window, but AFAICT it doesn't use any of the
GLX_EXT_buffer_age, GLX_OML_swap_method or GLX_INTEL_swap_event extensions =
to
find out what if any guarantees there are about the contents of the back bu=
ffer
after a buffer swap. blender's assumptions about that may happen to be valid
with DRI2, which can only use up to two buffers, but not with DRI3, which c=
an
use more.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--14695056080.8dD4.29921
Date: Tue, 26 Jul 2016 04:00:08 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comment=
# 8
on bug 97059<=
/a>
from Michel D=C3=A4nzer
I suspect this is a blender bug. It clearly doesn't render at =
all to the
corrupted parts of its window, but AFAICT it doesn't use any of the
GLX_EXT_buffer_age, GLX_OML_swap_method or GLX_INTEL_swap_event extensions =
to
find out what if any guarantees there are about the contents of the back bu=
ffer
after a buffer swap. blender's assumptions about that may happen to be valid
with DRI2, which can only use up to two buffers, but not with DRI3, which c=
an
use more.
You are receiving this mail because:
- You are the assignee for the bug.
=
--14695056080.8dD4.29921--
--===============1063886663==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1063886663==--