15 Replies Latest reply on Oct 30, 2011 7:25 PM by oxydius

    OpenVideo Decode crash in amdocl.dll

    oxydius

      The provided OVDecodeRender sample application works fine. However, OVD causes an OpenCL crash when a second session is created. The sample app is the easiest way to reproduce this. Simply create a dummy OVD session after the real one in OVDecodeTest.cpp :

       
          session = OVDecodeCreateSession(
              ovdContext, 
              ovDeviceID,
              profile,
              oFormat,
              oWidth,
              oHeight);

       
      +    OVDecodeCreateSession(
      +        ovdContext, 
      +        ovDeviceID,
      +        profile,
      +        oFormat,
      +        oWidth,
      +        oHeight);

       

      The second dummy session can be totally ignored, but the simple call to OVDecodeCreateSession invalidates the previous session in such a way that using it and calling OVDecodePicture returns a toxic cl_event. Using that event causes a 0xbaadf00d access violation in clWaitForEvents!

      AMD, please reproduce and release a hotfix as it's really bad and prevents OpenVideo adoption!

        • OpenVideo Decode crash in amdocl.dll
          oxydius

          I should mention this happens with Catalyst 11.1, 11.2, 11.3, 11.4, 11.5, 11.6, 11.7, 11.8 under Win7 x64, with Radeon 4350, 5450 and 6450.

          • OpenVideo Decode crash in amdocl.dll
            oxydius

            With Catalyst 11.9 RC, it doesn't even matter how many sessions are created. The unmodified OVDecodeRender sample app crashes reading 0xbaadf00d.

              • OpenVideo Decode crash in amdocl.dll
                oxydius

                Is anyone at AMD reading this forum? The streamdeveloper@amd.com address says this is the new place for OpenCL-related support requests. OpenVideo doesn't just randomly crash, it always crashes. Does your sample application work on your end? If it does, do you need any more information to reproduce? If not, is it an application or a driver problem?

                  • OpenVideo Decode crash in amdocl.dll
                    genaganna

                     

                    Originally posted by: oxydius Is anyone at AMD reading this forum? The streamdeveloper@amd.com address says this is the new place for OpenCL-related support requests. OpenVideo doesn't just randomly crash, it always crashes. Does your sample application work on your end? If it does, do you need any more information to reproduce? If not, is it an application or a driver problem?

                    Please take latest OVDecodeRender sample from http://developer.amd.com/sdks/AMDAPPSDK/samples/Pages/default.aspx. and try to run.

                      • OpenVideo Decode crash in amdocl.dll
                        oscarbarenys1

                        File is broken so says winrar! I have tried many times! fix it!

                          • OpenVideo Decode crash in amdocl.dll
                            genaganna

                             

                            Originally posted by: oscarbarenys1 File is broken so says winrar! I have tried many times! fix it!

                            Reported to respective person. It will be fixed soon.

                              • OpenVideo Decode crash in amdocl.dll
                                oxydius

                                Thanks, the zip file was fixed.

                                I just tried the new sample app on Win7 with two Radeon HD 6950 cards and latest 11.8 driver.

                                The 64-bit binary crashed the display driver, which restarted.

                                The 32-bit binary caused display glitches then crashed (hard reset) the computer.

                                What OS/hardware/driver combination is this being tested with? :-/

                                  • OpenVideo Decode crash in amdocl.dll
                                    oxydius

                                    Here was the output of the first run after the driver crashed :

                                    Platform 0 : Advanced Micro Devices, Inc.
                                    display devices 1
                                    ovDeviceID found!
                                    ovDeviceID value is 0000000001F7F950

                                    OVD_H264_HIGH_41

                                    oWidth=720 video_height=480
                                    Error: clCreateProgramWithSource failed. Error code : CL_INVALID_VALUE
                                    Create kernels failed!

                                    Frame: 0

                                    Decode_Parser_Render H.264

                                      • OpenVideo Decode crash in amdocl.dll
                                        genaganna

                                         

                                        Originally posted by: oxydius Here was the output of the first run after the driver crashed :

                                        Platform 0 : Advanced Micro Devices, Inc. display devices 1 ovDeviceID found! ovDeviceID value is 0000000001F7F950

                                        OVD_H264_HIGH_41

                                        oWidth=720 video_height=480 Error: clCreateProgramWithSource failed. Error code : CL_INVALID_VALUE Create kernels failed!

                                        Frame: 0

                                        Decode_Parser_Render H.264

                                        It is working fine with internal latest driver. Could you please tell us your SDK version, Driver version, OS and GPU?

                                        • OpenVideo Decode crash in amdocl.dll
                                          oxydius

                                          SDK 2.5

                                          Catalyst 11.8

                                          Windows 7 Ultimate x64

                                          Radeon HD 6950 x2

                                            • OpenVideo Decode crash in amdocl.dll
                                              genaganna

                                               

                                              Originally posted by: oxydius SDK 2.5

                                              Catalyst 11.8

                                              Windows 7 Ultimate x64

                                              Radeon HD 6950 x2

                                              Oxydius,

                                              There is a known crash issue on cayman. It will be fixed in upcoming releases.

                                                • OpenVideo Decode crash in amdocl.dll
                                                  oxydius

                                                  Alright, good to know. This should be in release notes. :)

                                                   

                                                  I tried on a different machine then, Win7 x64 with Radeon HD 6450 and Catalyst 11.8, SDK 2.5. The sample application works as-is, but adding a second unused OVDecodeCreateSession() call causes an access violation reading 0xffffffffffffffff at aticaldd64.dll!000000006918c539() within the clWaitForEvents call.

                                                  I'm using the following AMD/ATI modules :

                                                  amdocl64.dll C:\Windows\System32\amdocl64.dll 2, 5, 732, 1 18/08/2011 1:55 PM
                                                  atiadlxx.dll C:\Windows\System32\atiadlxx.dll 6.14.10.1068 28/07/2011 1:54 PM
                                                  aticaldd64.dll C:\Windows\System32\aticaldd64.dll 6.14.10.1523 28/07/2011 2:10 PM
                                                  aticfx64.dll C:\Windows\System32\aticfx64.dll 8.17.10.1091 28/07/2011 2:39 PM
                                                  atig6pxx.dll C:\Windows\System32\atig6pxx.dll 8.14.01.6226 28/07/2011 1:54 PM
                                                  atig6txx.dll C:\Windows\System32\atig6txx.dll 8.14.01.6226 28/07/2011 1:54 PM
                                                  atio6axx.dll C:\Windows\System32\atio6axx.dll 6.14.10.11005 28/07/2011 3:08 PM
                                                  OpenCL.dll C:\Windows\System32\OpenCL.dll 1.01.0.0 28/07/2011 2:48 PM
                                                  OVDecode64.dll C:\Windows\System32\OVDecode64.dll 28/07/2011 2:49 PM

                                                    • OpenVideo Decode crash in amdocl.dll
                                                      genaganna

                                                       

                                                      Originally posted by: oxydius Alright, good to know. This should be in release notes. :) 

                                                      I tried on a different machine then, Win7 x64 with Radeon HD 6450 and Catalyst 11.8, SDK 2.5. The sample application works as-is, but adding a second unused OVDecodeCreateSession() call causes an access violation reading 0xffffffffffffffff at aticaldd64.dll!000000006918c539() within the clWaitForEvents call.

                                                      I'm using the following AMD/ATI modules :

                                                      amdocl64.dll C:\Windows\System32\amdocl64.dll 2, 5, 732, 1 18/08/2011 1:55 PM atiadlxx.dll C:\Windows\System32\atiadlxx.dll 6.14.10.1068 28/07/2011 1:54 PM aticaldd64.dll C:\Windows\System32\aticaldd64.dll 6.14.10.1523 28/07/2011 2:10 PM aticfx64.dll C:\Windows\System32\aticfx64.dll 8.17.10.1091 28/07/2011 2:39 PM atig6pxx.dll C:\Windows\System32\atig6pxx.dll 8.14.01.6226 28/07/2011 1:54 PM atig6txx.dll C:\Windows\System32\atig6txx.dll 8.14.01.6226 28/07/2011 1:54 PM atio6axx.dll C:\Windows\System32\atio6axx.dll 6.14.10.11005 28/07/2011 3:08 PM OpenCL.dll C:\Windows\System32\OpenCL.dll 1.01.0.0 28/07/2011 2:48 PM OVDecode64.dll C:\Windows\System32\OVDecode64.dll 28/07/2011 2:49 PM

                                                      Thanks for reporting this issue. we also found this issue internally and looking at that issue.