CrashReportClient does'nt work in 4.12.2

Development Platform & Builds
, , ,
1

Hi!
It seems to be that CrashReportClient does not work on 4.12.2. After building project (Windows x64, with Frontend or with Editor) CrashReportClient.exe is included in build but it does’nt lauch when game crashes. At the same time crash report and minidump properly saved in %Project%/Saved/Logs.
I’ve try some manipulation with building options but nothing helped to me, but when I replace original CrashReportClient.exe with CrashReportClient.exe from 4.11 it works fine (lauches when game crashes and sending report).
I saw that CrashReportClient have been changed in 4.12 and there is some new options in config file, so maybe I make something wrong or miss something in configuration?

Please help!

2

Hello Karsten Maxim,

To test to ensure that it is or isn’t working correctly, can you please crash a project in 4.12.2 with the Debug Crash console command? Not all crashes will trigger Crash Reporter to appear but that particular one should. There were some changes to Crash Reporter recently to fix an issue but it shouldn’t cause it to no longer appear.

3

Hello !

I have done this test. Results:
CrashReportClient.exe (4.12) failed to start;
CrashReportClient.exe (4.11) success;

4

Thank you for testing that Karsten,

Are you using a source built engine perhaps? If so, another user reported this same issue a few days ago and we have a bug report in for it under the number UE-31938. This particular report mentions that it only occurs in engines built from source however and does not happen with binary builds, so if you are experiencing this with a build downloaded from the Epic Games Launcher, please let me know and we can continue. Otherwise, I’ll be marking this as resolved since the report is already in.

5

Oh, I’m sorry, I forgot to say about engine version. Yes I built engine from source.

Thank You!

6

Sorry to jump in here like this, but maybe my problem is related?

I have just tried to download and install UE from the site (16 July 2016) and I’m getting this message in a dialog box at the end of the install and whenever I try to start the software using the Epic icon (which does get installed on my desktop) :

“CrashReportClient has stopped working”
“A problem caused the program to stop working
correctly. Please close the program”

I don’t know what version to mention because it is whatever is current today and since the program doesn’t launch, I can’t tell.

I am using Vista 64 bit. I know it isn’t the recommended operating system, but it should still launch and just run slow.

7

Hello ,

Since it seems that CrashReportClient itself is crashing, we’ll need to some help from Windows here. Please take a look at this documentation. At the end you should end up with some logs that can give some information on what happened when you attempted to launch UE4. Could you upload those logs here?

8

Hi , Here is the log. I just tried to launch UE and it generated this log…Thanks,

Log Name: Application
Source: Application Error
Date: 18/07/2016 8:23:28 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: JonWoll-PC
Description:
Faulting application CrashReportClient.exe, version 4.12.0.0, time stamp 0x57683a09, faulting module MSVCP140.dll, version 6.0.6002.19346, time stamp 0x55024102, exception code 0xc0000135, fault offset 0x0006f49f, process id 0x77c, application start time 0x01d1e16cead16ffb.
Event Xml:

<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-07-19T03:23:28.000Z" />
<EventRecordID>226622</EventRecordID>
<Channel>Application</Channel>
<Computer>JonWoll-PC</Computer>
<Security />


<Data>CrashReportClient.exe</Data>
<Data>4.12.0.0</Data>
<Data>57683a09</Data>
<Data>MSVCP140.dll</Data>
<Data>6.0.6002.19346</Data>
<Data>55024102</Data>
<Data>c0000135</Data>
<Data>0006f49f</Data>
<Data>77c</Data>
<Data>01d1e16cead16ffb</Data>
9

Thank you for the information. From looking up the error code listed there, which is “0x80000000000000”, it seems like it could be a case of missing the related C++ distributables. It also may be helpful to verify your engine installation through the Epic Games Launcher to ensure that the installation worked correctly.

10

Thanks ,

I did try uninstalling it and then downloading and reinstalling it. Perhaps my copy of Vista is broken? Thanks for pointing me in a direction that I can investigate further.

11

It seems that it is a Vista issue. This was the information I was able to find which was from quite a while back. Unfortunately you’ll need to either get an older version of the engine or upgrade to a newer version of Windows.

12

I’m in the process of researching building a new computer, and I’ll buy a new operating system for it, so it will be the latest Windows, probably. I was hoping to give UE a try first to see how it works and what it does. I’ll look into an older version, I guess, or I’ll just wait until the new system is up and running in a couple of months.

Thanks for your help :slight_smile:

13

Hi , I’m experiencing this with the Epic Games Launcher build (4.12.5), I even reinstalled the launcher and the engine, but the crash reporter won’t show up.
In the crash reporter log I can see:

[2016.07.23-01.54.37:012][ 0]LogCrashDebugHelper:Warning: CrashDebugHelperConfig invalid
[2016.07.23-01.54.37:012][ 0]LogCrashDebugHelper:Warning: PDB Cache disabled
[2016.07.23-01.54.37:013][ 0]LogExit: Preparing to exit.

14

Well after trying and trying and trying I formatted my pc. Fresh windows 10 installation, fresh visual studio installation, fresh unreal engine installation and the Crash Report Client still isn’t working.
Here is the log file:

link text

15

When is this happening? Is it when you try to launch 4.12.5? Does the editor ever open? Do you ever see a crash reporter window?

If your engine is downloaded from the Epic Games Launcher, then this is a different issue from what the original poster was mentioning. Can you please make a new Answerhub post of your own? Feel free to link to it here and answer the questions that I asked in your new question.

It’s best if we split the different issues apart to avoid any confusion.