cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

peter_clark
Journeyman III

GPU PerfStudio 2.14 (and 2.15) - Cannot use frame debugger or profiler - immediately crashes

Every time I try to use the frame debugger or profiler I get the same error dialog:

Microsoft Visual C++ Runtime Library

Runtime Error!

Program: <my program's name>

R6025

- pure virtual function call

This happens the instant I try to use either of the features I mentioned (by click on their respective buttons). Note that I am able to use the API trace without issue.

I've tried this on two different applications with the exact same results:

  • A moderate size 3D game project (~90k LOC)
    • Normally uses OpenGL 3.2, but I have also tried using 4.2 with both a compatibility and core context with the same results.
    • External libraries used that affect graphics: SDL2 and GLEW.
    • After I click the frame debugger/profiler button my program's viewport is replaced by all blue for an instant before it crashes.
  • A tiny isolated sandbox that draws a red full screen quad with a simple shader.
    • Uses the maximum OpenGL context version it can obtain, on my machine I get a 4.4 compatibility context.
    • External libraries used that affect graphics: freeGLUT and GLEW.
    • After I click the frame debugger/profiler button it immediately crashes.

I have attached the sandbox project, both a prebuilt executable and the project/source files are included.

Note that both projects are 32-bit and are built using Visual Studio 2012.

Relevant specs for my machine:

  • Windows 8.1
  • AMD R7 260x
  • Catalyst Version 14.4 (Driver Packaging Version 14.10.1006-140417a-171099C)
  • OpenGL Version (from AMD Catalyst Control Center) 6.14.10.12874
0 Likes
1 Solution

Hi Peter,

This could be ralated to another issue with CodeXL. See Catalyst 14.4 and CodeXL crush. There's a known issue with the 14.4 driver and Southern Island cards. Try reverting your video drivers and see if that helps.

Previous video drivers can be found here:

Previous AMD Catalyst™ Display Drivers

Tony.

View solution in original post

0 Likes
10 Replies
derek_gladding
Journeyman III

Confirmed here as well.

Tried with many combinations of: 7770 / R7 260, Win7 / Win8.1 (including fresh OS install), Local/Remote server.

Simple test cases: glBenchmark and Doom3 both crash. Some systems report "pure virtual function call" as above, others BSOD.

Request: could AMD please make 2.13 available again until this is fixed?

0 Likes
cippyboy
Journeyman III

Same here, DX debugging hangs on start-up while GL debugging hangs when you go to the frame debugger but API trace does work.

0 Likes
bobwhitecotton
Adept III

Please note that an update (V2.15) has been posted which might fix your issue.  Please download and install the new release.

http://developer.amd.com/tools-and-sdks/graphics-development/gpu-perfstudio-2/

Let us know if it fixes your problem or not.

Thanks,

Bob

0 Likes

I just tried 2.15 on both applications and received the same error unfortunately.

0 Likes

Hi, we have a quick question. Are you using an AMD APU in your system? (i.e. an AMD CPU with its own built in graphics)

0 Likes

I've got an Intel i5 processor (which does have built in graphics). Just to note - I do successfully get my graphics context from the AMD GPU and not my integrated graphics.

In-case it helps here's what I get when in my sandbox project (in which I don't specify what version I want, which I believe just gives me the highest available):

Version: 4.4.12874 Compatibility Profile Context 14.100.0.0

Vendor: ATI Technologies Inc.

Renderer: AMD Radeon R7 200 Series

Shading: 4.30


Note that I have tried using a core context as well with no luck.

In my other project I explicitly ask for a 4.2 context and get it (also from the R7 GPU).

0 Likes

Just double checked to be sure I had tried the core context with 2.15 and verified it did the same. Also double checked and verified I did use 2.15 version of both client and server (I had 2.14 pinned to my start menu before so I was concerned), same result. I've removed 2.14 from my system now to be safe.

In-case it helps I've got the console output on the server up until when it crashes (filtering out my program's console output):

Message: PID:       5648 TID:       4456 GPUPerfServer : GPU PerfStudio Server - Version V2.15.2095.0

Message: PID:       5648 TID:       4456 GPUPerfServer : Using Logfile: C:\AMD\GPUPerfStudio\GPUPerfStudio2.15.2095.0\Server-Win32\pslog.txt

Successfully enabled DX Performance Counters in Driver

Message: PID:       5648 TID:       4456 GPUPerfServer : Available Wrappers:

Message: PID:       5648 TID:       4456 GPUPerfServer :    DX10Server.dll      V2.15.2095.0    DX10

Message: PID:       5648 TID:       4456 GPUPerfServer :    DX11Server.dll      V2.15.2095.0    DX11

Message: PID:       5648 TID:       4456 GPUPerfServer :    DX9Server.dll       V2.15.2095.0    DX9

Message: PID:       5648 TID:       4456 GPUPerfServer :    DXGIServer.dll      V2.15.2095.0    DXGI

Message: PID:       5648 TID:       4456 GPUPerfServer :    GLServer.dll        V2.15.2095.0    OpenGL

Message: PID:       5648 TID:       4456 GPUPerfServer : Starting web server on port 80

Message: PID:       5648 TID:       4456 GPUPerfServer : About to launch: W:\repositories\rg3d\root\source\projects\ping.exe

Message: PID:       5648 TID:       4456 GPUPerfServer : Params:

Message: PID:       5648 TID:       4456 GPUPerfServer : Working Directory:

Message: PID:       5648 TID:       4456 GPUPerfServer : strApp: W:\repositories\rg3d\root\source\projects\ping.exe

Message: PID:       5648 TID:       4456 GPUPerfServer : strCmdLine: W:\repositories\rg3d\root\source\projects\ping.exe

// My program's output would be here

// Click pause button here

Message: PID:       5648 TID:       5136 GPUPerfServer :   3: 127.0.0.1  - /5980/OpenGL/PushLayer=TimeControl

Message: PID:       5648 TID:       5136 GPUPerfServer :   4: 127.0.0.1  - /5980/OpenGL/TC/Settings.xml

Message: PID:       5648 TID:       5136 GPUPerfServer :   5: 127.0.0.1  - /5980/OpenGL/PushLayer=FrameCapture

Message: PID:       5648 TID:       5136 GPUPerfServer :   6: 127.0.0.1  - /5980/OpenGL/TC?realpause=True

Message: PID:       5648 TID:       5136 GPUPerfServer :   7: 127.0.0.1  - /5980/OpenGL/TC?Speed=0

Message: PID:       5648 TID:       5136 GPUPerfServer :   8: 127.0.0.1  - /5980/OpenGL/FC?HandleMapsOnCPU=False

Message: PID:       5648 TID:       5136 GPUPerfServer :   9: 127.0.0.1  - /5980/OpenGL/FC/Capture?Stream=0

Message: PID:       5648 TID:       5136 GPUPerfServer :  10: 127.0.0.1  - /5980/OpenGL/TC?PausedWithFrameCapture=True

Message: PID:       5648 TID:       5136 GPUPerfServer :  11: 127.0.0.1  - /5980/OpenGL/CommandTree.xml

// Click frame debug/profile here

Message: PID:       5648 TID:       5136 GPUPerfServer :  12: 127.0.0.1  - /5980/OpenGL/PushLayer=FrameDebugger

Message: PID:       5648 TID:       5136 GPUPerfServer :  13: 127.0.0.1  - /5980/OpenGL/FD/Stats.xml

Message: PID:       5648 TID:       5136 GPUPerfServer :  14: 127.0.0.1  - /5980/OpenGL/PopLayer

Message: PID:       5648 TID:       5136 GPUPerfServer :  15: 127.0.0.1  - /5980/OpenGL/PushLayer=FrameProfiler

Message: PID:       5648 TID:       5136 GPUPerfServer :  16: 127.0.0.1  - /5980/OpenGL/FP/CounterSelect.txt=0

Message: PID:       5648 TID:       5136 GPUPerfServer :  17: 127.0.0.1  - /5980/OpenGL/FP/CounterInfo.xml

Message: PID:       5648 TID:       5136 GPUPerfServer :  18: 127.0.0.1  - /5980/OpenGL/FP/Profiler.xml

// Crashes here

0 Likes

Tried 2.15, GL Debugging is still crashing like in the original post, DX11 though works fine, frame debugger, API Trace, etc

0 Likes

Hi Peter,

This could be ralated to another issue with CodeXL. See Catalyst 14.4 and CodeXL crush. There's a known issue with the 14.4 driver and Southern Island cards. Try reverting your video drivers and see if that helps.

Previous video drivers can be found here:

Previous AMD Catalyst™ Display Drivers

Tony.

0 Likes

After doing a clean install of the 13.12 driver the frame debugger and profiler both work! I'll stick to this driver version for now and will keep my eyes out for the next driver release.

Thanks!

0 Likes