Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CRASH] Setting the rate control method to peak constrained vbr crashes! #288

Open
LeadAssimilator opened this issue Jan 10, 2022 · 0 comments
Labels
fixed-in-future-release A fix has been made internally and is awaiting to be included in a future public driver release.

Comments

@LeadAssimilator
Copy link

When setting AMF_VIDEO_ENCODER_RATE_CONTROL_METHOD or AMF_VIDEO_ENCODER_HEVC_RATE_CONTROL_METHOD to AMF_VIDEO_ENCODER_RATE_CONTROL_METHOD_PEAK_CONSTRAINED_VBR or AMF_VIDEO_ENCODER_HEVC_RATE_CONTROL_METHOD_PEAK_CONSTRAINED_VBR a crash occurs inside amfrt32.dll or amfrt64.dll version 1.4.17.0.

The crash appears to stem from an uninitialized AMFVariantStruct used as the output parameter for the AMF_VIDEO_ENCODER_PRE_ANALYSIS_ENABLE or AMF_VIDEO_ENCODER_HEVC_PRE_ANALYSIS_ENABLE property which is internally retrieved when setting the rate control method property. During the get, AMFVariantClear is called on the uninitialized variant, and depending on what was on the stack, the type could inadvertently be string, wstring or interface which leads to freeing or dereferencing garbage, leading to the crash.

There is no newer version of drivers available for AMD Radeon Pro V520 MxGPU on AWS and this bug is preventing adoption of AMD over NVIDIA at this point. We need this fixed and a newer driver issued for the aforementioned gpu.

@rhutsAMD rhutsAMD added the fixed-in-future-release A fix has been made internally and is awaiting to be included in a future public driver release. label Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed-in-future-release A fix has been made internally and is awaiting to be included in a future public driver release.
Projects
None yet
Development

No branches or pull requests

2 participants