dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85613] still getting segfault with vdpau and r600g on Radeon 3850HD - have sample video
Date: Thu, 30 Oct 2014 07:23:50 +0000	[thread overview]
Message-ID: <bug-85613-502-xVud4353lT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-85613-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2486 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=85613

--- Comment #4 from Michel Dänzer <michel@daenzer.net> ---
>From bug 85268:

> ==13424== Invalid read of size 8
> ==13424==    at 0x1A6A4291: destroy_video_buffer_private (in /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
> ==13424==    by 0x1A6C0127: vl_video_buffer_destroy (in /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
> ==13424==    by 0x1A627314: vlVdpVideoSurfaceDestroy (in /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
> ==13424==    by 0x189B4092: SurfaceDestroy (in /usr/lib/vlc/plugins/vdpau/libvdpau_avcodec_plugin.so)
> ==13424==    by 0x30D0E8DCF4: picture_Release (in /usr/lib/libvlccore.so.8.0.0)
> ==13424==    by 0x30D0E6D095: ThreadDisplayPreparePicture (in /usr/lib/libvlccore.so.8.0.0)
> ==13424==    by 0x30D0E6D12B: ThreadDisplayPicture (in /usr/lib/libvlccore.so.8.0.0)
> ==13424==    by 0x30D0E6DEB2: Thread (in /usr/lib/libvlccore.so.8.0.0)
> ==13424==    by 0x30022080A3: start_thread (pthread_create.c:309)
> ==13424==  Address 0x6780940 is 480 bytes inside a block of size 10,760 free'd
> ==13424==    at 0x4A08E90: free (vg_replace_malloc.c:473)
> ==13424==    by 0x1A6A44CA: vl_mpeg12_destroy (in /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
> ==13424==    by 0x1A628489: vlVdpDecoderDestroy (in /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
> ==13424==    by 0x189B370D: Close (in /usr/lib/vlc/plugins/vdpau/libvdpau_avcodec_plugin.so)
> ==13424==    by 0x30D0E9028E: vlc_module_unload (in /usr/lib/libvlccore.so.8.0.0)
> ==13424==    by 0x1715EE48: vlc_va_Delete (in /usr/lib/vlc/plugins/codec/libavcodec_plugin.so)
> ==13424==    by 0x1715AA59: ffmpeg_GetFormat (in /usr/lib/vlc/plugins/codec/libavcodec_plugin.so)
> ==13424==    by 0x306F7FD5E0: ff_get_format (in /usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0)
> ==13424==    by 0x306F6DDBC8: decode_chunks (in /usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0)
> ==13424==    by 0x306F6DF8C8: mpeg_decode_frame (in /usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0)
> ==13424==    by 0x306F7FBE1A: avcodec_decode_video2 (in /usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0)
> ==13424==    by 0x1715C18C: DecodeVideo (in /usr/lib/vlc/plugins/codec/libavcodec_plugin.so)

Looks like VLC destroys the VDPAU surface after the VDPAU decoder, and the
Gallium VDPAU state tracker chokes on that.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3611 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

  parent reply	other threads:[~2014-10-30  7:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 17:47 [Bug 85613] New: still getting segfault with vdpau and r600g on Radeon 3850HD - have sample video bugzilla-daemon
2014-10-29 19:26 ` [Bug 85613] " bugzilla-daemon
2014-10-29 20:13 ` bugzilla-daemon
2014-10-30  7:21 ` bugzilla-daemon
2014-10-30  7:23 ` bugzilla-daemon [this message]
2014-10-30  8:34 ` bugzilla-daemon
2014-10-30  8:44 ` bugzilla-daemon
2014-10-30  9:08 ` bugzilla-daemon
2014-10-30  9:32 ` bugzilla-daemon
2014-10-30 10:04 ` bugzilla-daemon
2014-10-30 10:08 ` bugzilla-daemon
2014-10-30 10:10 ` bugzilla-daemon
2014-10-30 10:18 ` bugzilla-daemon
2014-10-30 10:46 ` bugzilla-daemon
2014-10-30 11:03 ` bugzilla-daemon
2019-09-18 19:17 ` 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-85613-502-xVud4353lT@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