# "profilegpu" crash "standalone game" on OSX

**URL:** <https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415>\
**Category:** Debugging, Optimization, & Profiling\
**Tags:** osx, unreal-engine, crash, bug-report, editor, question\
**Created:** [September 5, 2016, 10:30am UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415 "2016-09-05T10:30:27Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![NeWincpp](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@NeWincpp](https://forums.unrealengine.com/u/NeWincpp)\
**Post date:** [September 5, 2016, 10:30am UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/1 "2016-09-05T10:30:27Z")

</div>

Well everything is in the title, I just click on “standalone game” in UE4Editor and when I open the console then type “profilegpu” at the moment when I hit enter it crash with this log:  
[http://pastebin.com/raw/mvgmRsS3](http://pastebin.com/raw/mvgmRsS3) (given by OSX)  
[http://pastebin.com/raw/tS0c2q8u](http://pastebin.com/raw/tS0c2q8u) (given by unreal)

after some tests this bug exist with any type of project (C++ or blueprint) and with any blank project (I’ve tried side scroller, FPS and Third person template). To reproduce it:

1. create any type of blank project
2. (FPS blueprint for exemple) click
3. “standalone game” type “`” to open
4. the console type profile (to  
complete profileGPU)
5. press enter see and it your game  
crash

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_6e7b421a](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_6e7b421a](https://forums.unrealengine.com/u/anonymous_user_6e7b421a)\
**Post date:** [September 6, 2016, 2:34pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/2 "2016-09-06T14:34:53Z")

</div>

Hello NeWincpp,

Can you also provide me with some screenshots and steps to reproduce this issue in a blank project?

Is this a blueprint or code based project?

Please take a look at our **[How to Report a Bug](https://forums.unrealengine.com/showthread.php?29-How-to-report-a-bug)** sticky on the forums to get a solid idea of our usual requested information.

Let me know if you have further questions or need additional assistance.

Cheers,

---

<div class="post-metadata">

**Author:** ![NeWincpp](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@NeWincpp](https://forums.unrealengine.com/u/NeWincpp)\
**Post date:** [September 9, 2016, 1:35pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/3 "2016-09-09T13:35:18Z")

</div>

I’ve updated my post with the steps to reproduce the bug. but It seems that Unreal does not give me the log everytime…

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_6e7b421a](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_6e7b421a](https://forums.unrealengine.com/u/anonymous_user_6e7b421a)\
**Post date:** [September 9, 2016, 3:12pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/4 "2016-09-09T15:12:55Z")

</div>

I just tested the Profile GPU command in a new blank blueprint project within a Standalone window, and did not receive a crash.

Can you provide me with your systems specs?

Thanks,

---

<div class="post-metadata">

**Author:** ![NeWincpp](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@NeWincpp](https://forums.unrealengine.com/u/NeWincpp)\
**Post date:** [September 9, 2016, 3:24pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/5 "2016-09-09T15:24:41Z")

</div>

15-inch Mid 2015  
OSX 10.11.6 (El Capitan)  
Core i7-4870HQ with 16GB 1600 MHz DDR3  
Radeon R9 M370X (2048MB)

That’s weird my colleague with another with an nvidia-card wasn’t able to reproduce the bug either. I tried to delete unreal 4.13 and re-install it from the launcher ant that did _not_ fix the problem

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_6e7b421a](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_6e7b421a](https://forums.unrealengine.com/u/anonymous_user_6e7b421a)\
**Post date:** [September 12, 2016, 1:56pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/6 "2016-09-12T13:56:24Z")

</div>

Hey NeWincpp,

So you are actually in luck. I did some searching through our database this morning and found a nearly identical callstack crash that was found in by our QA team using a Macbook with a Radeon R9 M370X card. I am guessing it is the graphics card causing the problem, but our engineers will determine if that is in fact the case. Either way, it has been reported and moved to our Public issues tracker which you can navigate to by following the link below.

**[UE-35337](https://issues.unrealengine.com/issue/UE-35337)**

This issue is marked as critical so I expect it to be addressed very soon. Until then, let me know if you have further questions or need additional assistance.

Thank you,

---

<div class="post-metadata">

**Author:** ![NeWincpp](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@NeWincpp](https://forums.unrealengine.com/u/NeWincpp)\
**Post date:** [September 12, 2016, 2:12pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/7 "2016-09-12T14:12:08Z")

</div>

if it can help I also have a linux (gentoo) on this (with the R9 M370X) and the I could not reproduce the bug using the proprietary drivers (fglrx)

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_6888603d](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_6888603d](https://forums.unrealengine.com/u/anonymous_user_6888603d)\
**Post date:** [September 14, 2016, 9:41pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/8 "2016-09-14T21:41:06Z")

</div>

The JIRA number for this issue has been updated, please refer to [UE-36006](https://issues.unrealengine.com/issue/UE-36006) in future for this problem.

- You can workaround this issue by running with the -norhithread option from the command-line: the profilegpu command will work on Metal without the RHI thread & parallel execution.

---

<div class="post-metadata">

**Author:** ![Imagine-Games](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Imagine-Games](https://forums.unrealengine.com/u/Imagine-Games)\
**Post date:** [March 21, 2017, 1:22am UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/9 "2017-03-21T01:22:13Z")

</div>

im having the same issue both with my native graphics card nividia 750m and external 980Ti on mac… as soon as that command goes in (even in play in editor mode) the entire engine crashes… please please work on this bug guys, i really need to profile my games

---

<div class="post-metadata">

**Author:** ![NeWincpp](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@NeWincpp](https://forums.unrealengine.com/u/NeWincpp)\
**Post date:** [March 21, 2017, 1:44am UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/10 "2017-03-21T01:44:35Z")

</div>

you can vote here: [Unreal Engine Issues and Bug Tracker (UE-35337)](https://issues.unrealengine.com/issue/UE-35337) if you want this bug to get attention

---

<div class="post-metadata">

**Author:** ![Imagine-Games](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Imagine-Games](https://forums.unrealengine.com/u/Imagine-Games)\
**Post date:** [March 21, 2017, 5:00pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/11 "2017-03-21T17:00:34Z")

</div>

, I tried running the command profileGPU -norhithread and ue4 still crashes

---

<div class="post-metadata">

**Author:** ![Imagine-Games](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Imagine-Games](https://forums.unrealengine.com/u/Imagine-Games)\
**Post date:** [March 21, 2017, 5:23pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/12 "2017-03-21T17:23:23Z")

</div>

i voted, but there seems to be only 1 vote, did you vote?

---

<div class="post-metadata">

**Author:** ![Imagine-Games](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Imagine-Games](https://forums.unrealengine.com/u/Imagine-Games)\
**Post date:** [March 21, 2017, 5:24pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/13 "2017-03-21T17:24:44Z")

</div>

NEWIncpp they changed the bug to [Unreal Engine Issues and Bug Tracker (UE-36006)](https://issues.unrealengine.com/issue/UE-36006) please submit a vote, I already did

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_6888603d](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_6888603d](https://forums.unrealengine.com/u/anonymous_user_6888603d)\
**Post date:** [March 21, 2017, 5:26pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/14 "2017-03-21T17:26:58Z")

</div>

You have to run the standalone game executable from the command-line (i.e. Terminal) and add the -norhithread as a command-line argument for this to work. It is not something you add to the profilegpu command in-game.

---

<div class="post-metadata">

**Author:** ![Imagine-Games](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Imagine-Games](https://forums.unrealengine.com/u/Imagine-Games)\
**Post date:** [March 21, 2017, 9:19pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/15 "2017-03-21T21:19:15Z")

</div>

let me see if I understand… I tried running the command in the console both in a play in editor window and as a standalone game… it crashed as soon as I hit enter… what you are saying is for me to build the game and before launching the game I should launch instead from terminal like example: “run game.app -norhithread” ???

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_6888603d](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_6888603d](https://forums.unrealengine.com/u/anonymous_user_6888603d)\
**Post date:** [March 21, 2017, 9:29pm UTC](https://forums.unrealengine.com/t/profilegpu-crash-standalone-game-on-osx/369415/16 "2017-03-21T21:29:37Z")

</div>

1. Open Terminal.
2. Drag your application onto the Terminal window, which will add the path to the current line
3. Onto that add: /Contents/MacOS/ -norhithread
4. Hit enter.

Now once you are in-game the profilegpu command should work from the in-game console.
