From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 85613] still getting segfault with vdpau and r600g on Radeon 3850HD - have sample video Date: Thu, 30 Oct 2014 10:08:14 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1791724460==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C65856E58E for ; Thu, 30 Oct 2014 03:08:13 -0700 (PDT) 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 --===============1791724460== Content-Type: multipart/alternative; boundary="1414663693.E04c16F0.24935"; charset="UTF-8" --1414663693.E04c16F0.24935 Date: Thu, 30 Oct 2014 10:08:13 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D85613 --- Comment #10 from Christian K=C3=B6nig --- (In reply to Andreas Boll from comment #8) > It seems Arthur is using shader-based decoding instead of UVD based > decoding, which is less tested nowadays. Correct, and the problem is well known. It's just that the shader based decoding has a race condition when destroying surfaces. If the surfaces are destroy before the decoder it works fine (like mplayer/= mpv does it), but if the surfaces are destroyed after the decoder is destroyed = you run into this crash. --=20 You are receiving this mail because: You are the assignee for the bug. --1414663693.E04c16F0.24935 Date: Thu, 30 Oct 2014 10:08:13 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 10 on bug 85613<= /a> from Christian K=C3=B6nig 
(In reply to Andreas Boll from comment #8)
> It seems Arthur is using shader-based decoding i=
nstead of UVD based
> decoding, which is less tested nowadays.

Correct, and the problem is well known. It's just that the shader based
decoding has a race condition when destroying surfaces.

If the surfaces are destroy before the decoder it works fine (like mplayer/=
mpv
does it), but if the surfaces are destroyed after the decoder is destroyed =
you
run into this crash.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1414663693.E04c16F0.24935-- --===============1791724460== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1791724460==--