From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73457] mpeg4 through vdpau randomly either correct or garbled (on same file!)
Date: Wed, 16 Jul 2014 19:29:38 +0000 [thread overview]
Message-ID: <bug-73457-502-xi3YCbGtAj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73457-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1414 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73457
--- Comment #14 from Fabrice Bellet <fabrice@bellet.info> ---
Hi!
I observe the same problem too. The jpeg file of the garbled output is very
similar to what I see. Tested with upstream mesa/xorg, in a fedora 20 x86_64,
[AMD/ATI] Cape Verde PRO [Radeon HD 7750 / R7 250E].
I made some traces at the libvdpau level (VDPAU_TRACE env vars), that I can
provide if needed. They don't seem to present major differences between
situations with and without corruption. I tried to serialize the vdpau calls
with a mutex without more success, I played with the number of surfaces too, no
difference. libefence didn't help.
It looks like there may be a cache warmness effect at play, because it seems to
me that --even if the problem occurs mainly in a random way-- it can more
easily be triggered after a fresh boot, than after a couple of retries on the
same file. Also another feeling is that the bug is more easily triggered with
gstreamer-vaapi + vdpau, than with mplayer or vlc, maybe because gst can burst
a bunch of hw decoding operations on different surfaces before switching to the
rendering thread ? vlc and mplayer invoke vdpau in a more *ordered* way.
I also confirm point 3 of the initial reporter : the corruption may extend to
artifacts appearing *outside* the player window.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2252 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-07-16 19:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 22:41 [Bug 73457] New: mpeg4 through vdpau randomly either correct or garbled (on same file!) bugzilla-daemon
2014-01-09 22:42 ` [Bug 73457] " bugzilla-daemon
2014-01-09 22:42 ` bugzilla-daemon
2014-01-09 22:43 ` bugzilla-daemon
2014-01-09 22:44 ` bugzilla-daemon
2014-01-09 22:57 ` bugzilla-daemon
2014-01-09 23:00 ` bugzilla-daemon
2014-01-09 23:05 ` bugzilla-daemon
2014-01-09 23:17 ` bugzilla-daemon
2014-01-09 23:22 ` bugzilla-daemon
2014-01-09 23:25 ` bugzilla-daemon
2014-01-09 23:26 ` bugzilla-daemon
2014-04-20 8:18 ` bugzilla-daemon
2014-04-20 8:19 ` bugzilla-daemon
2014-07-16 19:29 ` bugzilla-daemon [this message]
2014-07-17 15:26 ` bugzilla-daemon
2014-07-20 23:17 ` bugzilla-daemon
2019-09-18 19:12 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-73457-502-xi3YCbGtAj@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox