Hi ,
The crash reporter does run. Similar to above we have the same thing happening on our client builds and we have to ask our testers to copy and paste whats inside the reporter so we can get that info. Unfortunately we don’t have access to %appdata% on our server hardware, just the logs so I can’t say if its available in that directory.
Depending on your setup, you might have CRC logs in Engine\Programs\CrashReportClient\Saved\Logs
Hi ,
We won’t have access to that either, we need the info to be dumped into the game log. What could we be missing, or what changed that would prevent the callstack from dumping into our game log like it was previously?
I feel like it should be noted that this has been a thing that we’ve simply been dealing with since as early as January, so this may have been caused by a change as far back as 4.10?
Right this is something I’m hearing regularly about Windows. I think we stopped attempting to walk the stack in the crashing app because it wasn’t reliable during crash conditions. We only attempt this in the Crash Report Client or on the crash server. It sounds like we should be adding the callstack back into the log, if possible. Do you see a crash context and minidump saved to the game’s log folder?
I do, yeah and can ask testers for that but its something we don’t have access to on the servers. A conversation that needs to be had with our provider but it’d also just be easier to have the full callstack in the log.
Okay, I have a ticket to fix the missing callstacks in Windows logs (UE-25474). I’ve linked it to this thread in our database.
This is fixed and going into 4.13. Callstack is written to the log on Windows.
When your packaged server crash (assuming windows server), did it generate .dmp files for you?
For me it generates crash folders, but the server crash folder doesn’t have the .dmp file in it. Neither it get’s uploaded to the CRC.
Only the client crashlog and .dmp is getting uploaded.