[4.12.4] No Crash Reporter on crash

I am using 4.12.4 that supposedely has a fix for this issue. Here’s log from \AppData\Local\CrashReportClient\Saved\Logs\

Log file open, 06/29/16 16:04:25
LogPlatformFile: Not using cached  wrapper
LogInit:Display: RandInit(837501615) SRandInit(837501616).
LogTaskGraph: Started task graph with 3 named threads and 6 total threads with 1 sets of task threads.
LogInit: Version: 4.12.4-3028348+++UE4+Release-4.12
LogInit: API Version: 2992821
LogInit: Net Version: 3028348
LogInit: Compiled (64-bit): Jun 27 2016 09:42:17
LogInit: Compiled with Visual C++: 19.00.23026.00
LogInit: Build Configuration: Shipping
LogInit: Branch Name: ++UE4+Release-4.12
LogInit: Command line: "..\..\..\Engine\Binaries/Win64/CrashReportClient.exe"  -AppName=UE4-RoomEditor -CrashGUID=UE4CC-Windows-BBE05E1F451CEDBC8C4BCFB1436365BA_0000 -DebugSymbols=..\..\..\Engine\Intermediate\Symbols
LogInit: Base directory: C:/Program Files (x86)/Epic Games/4.12/Engine/Binaries/Win64/
LogInit: Installed Engine Build: 1
LogInit: Presizing for max 100000 objects, including 0 objects not considered by GC, pre-allocating 0 bytes for permanent pool.
LogInit: Object subsystem initialized
[2016.06.29-13.04.25:863][  0]LogInit: Computer: DESKTOP-1PB2ALT
[2016.06.29-13.04.25:863][  0]LogInit: User: DreamVR2
[2016.06.29-13.04.25:863][  0]LogInit: CPU Page size=65536, Cores=4
[2016.06.29-13.04.25:863][  0]LogInit: High frequency timer resolution =2.648438 MHz
[2016.06.29-13.04.25:863][  0]LogMemory: Memory total: Physical=8.0GB (8GB approx)
[2016.06.29-13.04.25:863][  0]LogMemory: Platform Memory Stats for Windows
[2016.06.29-13.04.25:863][  0]LogMemory: Process Physical Memory: 24.16 MB used, 24.16 MB peak
[2016.06.29-13.04.25:863][  0]LogMemory: Process Virtual Memory: 50.62 MB used, 50.62 MB peak
[2016.06.29-13.04.25:863][  0]LogMemory: Physical Memory: 5196.89 MB used, 8144.64 MB total
[2016.06.29-13.04.25:863][  0]LogMemory: Virtual Memory: 203.20 MB used, 134217728.00 MB total
[2016.06.29-13.04.25:866][  0]LogTextLocalizationManager: No translations for ('ru-RU') exist, falling back to 'en' for localization and internationalization data.
[2016.06.29-13.04.25:908][  0]LogPackageLocalizationCache: Processed 2 localized package path(s) for 1 prioritized culture(s) in 0.000181 seconds
[2016.06.29-13.04.25:908][  0]CrashReportClientLog: CrashReportReceiverIP: http://crashreporter.epicgames.com:57005
[2016.06.29-13.04.25:908][  0]CrashReportClientLog: DataRouterUrl: https://datarouter-public-service-prod06.ol.epicgames.com/datarouter/api/v1/public/data
[2016.06.29-13.04.25:909][  0]LogCrashDebugHelper: DepotName: //UE4/Release-4.12
[2016.06.29-13.04.25:909][  0]LogCrashDebugHelper: BuiltFromCL: 3028348
[2016.06.29-13.04.25:909][  0]LogCrashDebugHelper: EngineVersion: 4.12.4-3028348+++UE4+Release-4.12
[2016.06.29-13.04.25:909][  0]LogCrashDebugHelper:Warning: CrashDebugHelperConfig invalid
[2016.06.29-13.04.25:909][  0]LogCrashDebugHelper:Warning: PDB Cache disabled
[2016.06.29-13.04.25:909][  0]LogExit: Preparing to exit.
[2016.06.29-13.04.25:909][  0]LogObj: Freed 0b from 0 cluster array pools.
[2016.06.29-13.04.25:909][  0]LogExit: Object subsystem successfully closed.
[2016.06.29-13.04.25:909][  0]LogModuleManager: Shutting down and abandoning module CrashDebugHelper (2)
[2016.06.29-13.04.25:909][  0]LogModuleManager: Shutting down and abandoning module CoreUObject (1)
[2016.06.29-13.04.25:909][  0]LogExit: Exiting.
[2016.06.29-13.04.25:910][  0]Log file closed, 06/29/16 16:04:25

Hey Alekseyllin-

Thank you for letting us know that this was still occurring. I have reopened UE-31938 which was the original report for this issue for further investigation. In case it helps you, this bug only affects source built versions of the engine. If you are able to use the binary version of 4.12.4 then the crash report window will open.

Cheers

This is a different problem I think. The log doesn’t include the error message I fixed last time. I’ll try repro’ing with a fresh download of 4.12.4.

Doesn’t repro for me with a fresh download of 4.12.4.

Steps:

  • Download and install 4.12.4 from github
  • Open solution and build UE4 editor (Development Editor), CrashReportClient (Shipping) and ShaderCompileWorker (Development Editor).
  • Run editor and crash with “debug crash”
  • CRC appears and submits crash to database successfully.

Hi , I’m having this exact same problem with the Epic Launcher version of the engine (4.12.5). I tried uninstalling everything, including the launcher, then cleaning the installation directories, as well as appdata directories, and reinstalled without luck. CrashReportClient won’t show no matter what I do.
My CrashReportClient log:
link text

Hey Storngrir-

In the Launcher, can you click the dropdown arrow next to Launch for 4.12.5 and select Options and check that “Editor symbols for debugging” is checked? If this is checked for you, can you add a screenshot of the error you see when a crash does occur?

Hey , I’m getting the same problem with a Fresh 4.12.5 with debugger symbols enabled. Also there is no displayed error. UE4 simply quits to desktop.

CrashReportClient log:

Actual crash log:

I’m happy to give out any more info if it’ll help resolve this issue, as it’s very difficult to debug without any crash feedback.
(Unless there’s a log somewhere that shows the same crash log that normally shows in the reporter?

Hey -

The end of the crash log should continue most of the same information that the crash report client does. In this case it appears the crash was caused by an array index that was being being outside the range of the array. You mentioned the debugger symbols, are you using the binary version of the engine from the Launcher? If so, can you also let me know if the crash report client opens if you create a new project and use the “debug crash” console command?

Answer to this question worked for me: https://answers.unrealengine.com/questions/453736/engine-crashes-instantly-what-to-do.html