2 Replies Latest reply on Nov 3, 2009 5:23 PM by jonmarbach

    FirePro driver slows down Visual Studio 2005 debugging tremendously

      5-10x slower! Anyone else expreriencing this?

      I've just recently begun to debug on AMD/ATI graphics hardware and the graphics driver has some unexplainable slowdown for VS2005 debugging that makes development darn near impossible.

      If I switch to an NV card in the exact same machine the debug speed issue goes away, so I feel that I've isolated the problem to the ATI driver. I'm running XP x64 on an old HP xw9300 dual Opteron machine.

      I know I'm not being very specific on the problem but here are some numbers: stepping over a relatively simple line of code is taking about 6 seconds for each line - normally (i.e with Nvidia hardware) the response is nearly-instantaneous. Also, at application exit, there is a 45-second delay or more, whereas normally the teardown only takes a few seconds.

      Incidentally, I'm seeing many messages like this in the VS output window:

      fnCallReturnMessage::WM_WINDOWPOSCHANGING: uID = 0


      Any help or advice would be appreciated, as my AMD/ATI developer experience is  less than stellar right now.