Information
I have verifed my game files (Steam only)
YesI have disabled all mods
YesI am running the latest game update
YesRequired
Summary
Crash Reporter: "Failed to upload crash report"Description
My game crashed, after I had been playing for an hour or so, I will report a separate bug on that issue.I am not sure whether this is the best place to post this, as the crash reporter is probably used for all PDX games, however, the issue might be due to some combination of CK3 and the Crash Reporter.
When uploading the crash report, it will says that it failed to do so, however, it seems like a partial error, which I can see by analyzing the HTTP calls that the application makes.
It appears that it successfully uploads the mini-dump file and my system details correctly, but fails on all subsequent uploads.
The subsequent uploads appear to be:
* exception.txt
* last_save.ck3
* debug.log
* error.log
* game.log
* meta.yml
* pdx_settings.txt
* user_crash_report.txt
These all fail with error code 500 (Internal Server error), and return the following error in the response body:
{"error":{"code":65536, "message":"unknown object"}}
Detailed list of calls that fail:
POST /paradoxinteractive/9912f4aa278a6f29c6c2f1c8a4c18b4d9e0c4b42b8e5394f28f4889efbf8ceef/minidump&object=aedd0100-c7e7-110a-0000-000000000000&attachment_name=debug.log HTTP/1.1
POST /paradoxinteractive/9912f4aa278a6f29c6c2f1c8a4c18b4d9e0c4b42b8e5394f28f4889efbf8ceef/minidump&object=aedd0100-c7e7-110a-0000-000000000000&attachment_name=error.log HTTP/1.1
POST /paradoxinteractive/9912f4aa278a6f29c6c2f1c8a4c18b4d9e0c4b42b8e5394f28f4889efbf8ceef/minidump&object=aedd0100-c7e7-110a-0000-000000000000&attachment_name=game.log HTTP/1.1
POST /paradoxinteractive/9912f4aa278a6f29c6c2f1c8a4c18b4d9e0c4b42b8e5394f28f4889efbf8ceef/minidump&object=aedd0100-c7e7-110a-0000-000000000000&attachment_name=meta.yml HTTP/1.1
POST /paradoxinteractive/9912f4aa278a6f29c6c2f1c8a4c18b4d9e0c4b42b8e5394f28f4889efbf8ceef/minidump&object=aedd0100-c7e7-110a-0000-000000000000&attachment_name=pdx_settings.txt HTTP/1.1
POST /paradoxinteractive/9912f4aa278a6f29c6c2f1c8a4c18b4d9e0c4b42b8e5394f28f4889efbf8ceef/minidump&object=aedd0100-c7e7-110a-0000-000000000000&attachment_name=user_crash_report.txt HTTP/1.1
This call succeeds (this should be the one uploading the dump file in the body of the request and my system information in the query parameters):
POST /paradoxinteractive/9912f4aa278a6f29c6c2f1c8a4c18b4d9e0c4b42b8e5394f28f4889efbf8ceef/minidump&SCMCommit=6dc0ab180c85f57b00a73546e4d1be69001c0279&AppName=Crusader%20Kings%20III&GPUId=8644&DateTime=%222023-05-14%2023:25:50%20+0200%22&AppVersion=1.9.0.3&Platform=Windows&SCMTimeStamp=%222023-05-11%2020:50:12%20+0000%22&Architecture=64-bit&SCMBranch=release/1.9.0.3&BuildType=ReleaseLto&Store=steam&OperatingSystem=Windows%2010%20x86_64&SystemLanguage=en&CPUModel=Intel(R)%20Core(TM)%20i7-4771%20CPU%20@%203.50GHz&CPUSpeed=3500&CPUPhysicalCores=4&CPULogicalCores=8&SystemMemory=32704&LaunchArguments=--gdpr-compliant%20--nakama%20--paradox-account-userid=%22%22%20--pdx-launcher-session-token=%22%22%20--simultaneouschunks=%22%22&GPUName=NVIDIA%20GeForce%20GTX%201660%20SUPER&GPUVendor=nVidia&GPUDedicatedMemory=5980&DLC_1=Fashion%20of%20the%20Abbasid%20Court&DLC_2=The%20Northern%20Lords&DLC_3=Garments%20of%20the%20Holy%20Roman%20Empire&DLC_4=The%20Fate%20of%20Iberia&DLC_5=The%20Royal%20Court HTTP/1.1
Connect call:
CONNECT submit.backtrace.io:443 HTTP/1.1
Host: submit.backtrace.io:443
HTTP/1.1 200 Connection Established
StartTime: 23:34:17.859
Connection: close
Notes:
* Not using the latest DLC.
* I am using Fiddler to collect the HTTP communication, this adds some custom headers to the communications, but should not cause any issues or obfuscate anything.
Attachments:
crash reporter error.png - Shows the crash reporter erroring after clicking send.
crash reporter comms (headers only).txt - Shows the headers of the failing crash reporter HTTP communication You should prefer to download the archive "crash report comms.saz" instead, and use it with fiddler or extract it as a zip-archive.
crash report comms.txt - The full communications in ANSI text encoding.
crash report comms.zip - The full communications as a Fiddler session archive, this can be unpacked as a zip file, e.g with 7-Zip or loaded into Fiddler Classic. The real extension of this is "saz", but I had to change it due to your restrictions, you may have to change it back, if you want to load it into Fiddler Classic.
http calls overview.png - Shows the failing HTTP calls from Fiddler Classic in an image.
ck3_20230514_232550.zip - The folder of the crash zipped.
dlcs.png - These are the DLCs that I have installed.
Steps to reproduce
1. Updated my game to the newest version.2. Played the game.
3. Encountered a crash to desktop.
4. Wrote a description into the crash reporter.
5. Click 'Send'
6. Now it should show you an error dialogue saying "An Error Occurred" - "Failed to upload the crash report"
Game Version
1.9.0.3Platform
WindowsAdditional Information
Affected Feature
- Crashes
Save Game
View attachment last_save.ck3View attachment ck3_20230514_232550.zipView attachment crash report comms.txtView attachment crash report comms.zipView attachment crash reporter comms (headers only).txt
View attachment last_save.zip
Other Attachments
View attachment last_save.ck3View attachment ck3_20230514_232550.zipView attachment crash report comms.txtView attachment crash report comms.zipView attachment crash reporter comms (headers only).txtView attachment last_save.zip
Last edited:
