1 Reply Latest reply on Jan 7, 2013 2:05 AM by binying

    amdocl_as.exe and/or amdocl_ld.exe orphaned processes?


      The platform I am using is OpenCL 1.2 AMD-APP (1016.4), APP SDK 2.8.

      When I run my program from visual studio (2010), nothing out of the ordinary happens. However, when I collect an application trace using the APP Profiler Session Explorer, the cmd window in which my program runs does not close. The profiler does produce realistic and usable results.


      A little investigation using the sysinternals process explorer showed that two processes, amdocl_as.exe and amdocl_ld.exe are in a suspended state. Closing visual studio doesn't solve the problem of the open cmd window, but killing those two processes does. Did anyone experience the same problem, or is anyone able to reproduce this behavior?


      If needed, I will strip down my program to make a minimal test case, when time permits.