Using "profilegpu" from a "Standalone Game" (running in it's own process outside the editor) causes UE4 to crash

Development Platform & Builds Debugging, Optimization, & Profiling
, ,
1

link text
Branch: I have this issue in both 4.6 preview and 4.5.1 binaries downloaded from the Unreal Launcher.

Build version: 4.6.0-2357962+++depot+UE4-Releases+4.6

Detailed description of the issue: Using “profilegpu” through console or ctrl+shift+, hotkey within a standalone process causes it to crash.

Screenshots/Link to video: http://youtu.be/NpDWkudJ3vE

Repro Steps

Action 1 Create a new “blank” blueprint project with default settings.

Action 2 When the project opens, click Play->“Standalone Game” mode.

Action 3 Press ctrl+shift+, or type “profilegpu” into the console of the standalone process and the standalone process.

This occurs 100% of the time for me (only step three is actually required).

System Specs: Win8.1 i7 16gbram 760gtx.

See attached dxdiag.txt, DMP and LOG files.

2

Hey tmek,

I wasn’t able to reproduce this crash as described. It looks like your crash log is truncated. Would you mind getting this crash again and sending us a fresh log? Thanks!

3

Hi Ben,

I created a new blank project (this was in 4.6 preview) opened up the default level, launched in Standalone Process and typed “profilegpu” in the console. It crashed and I zipped up everything in the project Saved\Logs folder as Logs2.zip

Seems like it’s this…

[2014.11.21-19.17.44:819][589]LogWindows: === Critical error: ===
Fatal error: [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.6\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp] [Line: 650]
Rendering thread exception:
Assertion failed: BytesPerPixel [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.6\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11RenderTarget.cpp] [Line: 573]

4

The one thing that might be unusual about my machine is that I have an Oculus Rift DK2. Maybe something to do with their special drivers that allow for direct to Rift mode for the GPU access?

5

Holy Moly! It is the DK2 being connected that causes this!

If I unplug it (hdmi cable) or press the power button to turn it off I do NOT get the crash. When it’s plugged in and powered (even in standby mode with orange light) I DO get the crash.

So the bug report needs to be updated to reflect this happens with DK2. Although hopefully you guys can still resolve this because we can’t enter and do profiling in “STEREO ON” mode without the hmd connected.

Thanks!
Thomas Kadlec

6

Hi tmek,

I was able to reproduce your issue and have entered it as JIRA UE-5752 in our tracking software. You’re correct, it only happens while a DK2 is plugged in. Our developers will be looking into it further.

As a temporary workaround, see if you can enter Stereo mode and then input the ProfileGPU command.

Cheers,

TJ

7

Yes! Switching into stereo mode first and then running ProfileGPU does work!
(I guess it has something to do with waking up the DK2s screen vs it being in sleep mode)

Thanks!