Bug 78641

Summary: Radeon makes Flash player with VDPAU enabled hang at vlVdpDecoderDestroy → flush → radeon_drm_ws_queue_cs
Product: Mesa Reporter: Marco Trevisan (Treviño) <mail>
Component: Drivers/Gallium/r600Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: 10.1   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: Radeon deadlock with Flash + VDPAU

Description Marco Trevisan (Treviño) 2014-05-12 23:48:31 UTC
Created attachment 98951 [details]
Radeon deadlock with Flash + VDPAU

1) Enable VDPAU support in flash player [1]
2) Visit web pages such as [2] (in that page the hang happens
   when the AD has been played and the actual video should start).

At this point the flash player hangs (plugin-container process with firefox), and there's no way to resume it other than killing the parent process.

It seems like a deadlock, see the attached backtrace; not sure if this has something in common with Bug 70123.
This is when using mesa 10.1 (4a86465) in Ubuntu 14.04.

[1] echo -e "EnableLinuxHWVideoDecode = 1\nOverrideGPUValidation = 1" >> /etc/adobe/mms.cfg
[2] http://video.corriere.it/i-ragazzi-anni-90-come-eravamo/9fd1a13c-d9b5-11e3-8b8a-dcb35a431922
Comment 1 Marco Trevisan (Treviño) 2014-05-13 00:14:24 UTC
Ah, this is not happening when using intel, then I suppose this is not an issue of the flash blob.
Comment 2 Grigori Goronzy 2014-05-13 00:18:25 UTC
It's not happening with Intel because the drivers don't support VDPAU.
Comment 3 Marco Trevisan (Treviño) 2014-05-13 00:30:25 UTC
(In reply to comment #2)
> It's not happening with Intel because the drivers don't support VDPAU.

Yes, of course... But I meant using the VDPAU support thought va_gl.
Also if VDPAU is not using mesa, in that case, I guess that if the problem would be in flash, then it would have hanged even when using va_gl, isn't it? :o
Comment 4 GitLab Migration User 2019-09-18 19:16:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/509.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.