Logs and crash dumps are truncated on upload to Sentry

[Edstub207]

Environment

How do you use Sentry?
Sentry.io

Which version of the SDK?
0.4.0

How did you install the package? (Git-URL, Assetstore)
Download from Git

Which version of Unreal?
5.1.1

Is this happening in Unreal (editor) or on a player like Android, iOS, Windows?
Server (Deployed in a Linux Container) but seeing similar behavior with logs for the editor

Steps to Reproduce

1. Boot the editor (Or server)
2. Crash
3. Observe logs are truncated (vs locally on the machine) and crash dumps aren't uploaded

Expected Result

Logs are fully uploaded and crash dumps are uploaded

Actual Result

[2023.05.03-21.12.06:572][995]LogStreaming: Display: 24.678 ms for processing 1992838 objects in RemoveUnreachableObjects(Queued=0, Async=0). Removed 1 (1160->1159) packages and 1 (2492->2491) public exports.
[2023.05.03-21.12.35:095][848]LogOutputDevice: Warning: 

Script Stack (0 frames) :

Any logs or screenshots

[tustanivsky]

Does this issue occur when using the Crash Reporter for crash capturing? Or this is something you're facing with when crashes are captured by sentry-native?

[Edstub207]

@tustanivsky we currently have the following options, although, we are on 5.1.1 and I just noticed it says 5.2 is required for the Automatic Crash reporting (Which IIRC is the native integration?)

[Edstub207]

@tustanivsky Bumping this :)

[tustanivsky]

@Edstub207 Alright, I've managed to reproduce this with 0.6.0 when running a Linux Server build on WSL. Apparently, sentry-native which plugin uses under the hood picks up a log file whenever a crash occurs and sends it to Sentry right away while Unreal is still about to write some stuff into it.

Starting from UE 5.2 we can use sentry-native for crash capturing on Windows so I'll try that out there as well in order to understand if it's something platform specific.

UPD: Same behavior on Windows.

[Edstub207]

Hi @tustanivsky this is pretty important with tracking crashes - Is there any update on this?

We've just upgraded to 5.2.1 what is the migration steps for the new sentry-native method? I presume we need to somehow disable the crash reporter and enable the correct solution in the Sentry Plugin?

[tustanivsky]

Hi @tustanivsky this is pretty important with tracking crashes - Is there any update on this?

Hey @Edstub207, there is no fix available for this issue yet. As mentioned before it seems to be expected sentry-native/crashpad behavior atm. In the latest plugin release 0.8.0 we've introduced an API allowing to pre-process captured events before sending them to Sentry, so I'll check if it's possible to add some custom logic there that might help us to get the full logs/dump files uploaded.

We've just upgraded to 5.2.1 what is the migration steps for the new sentry-native method? I presume we need to somehow disable the crash reporter and enable the correct solution in the Sentry Plugin?

In UE 5.2 you can check the Enable automatic crash capturing toggle in the plugin's settings menu which allows capturing crashes with sentry-native instead of having to use CRC. Keep in mind that it takes effect on Windows only. In order to disable the crash reporter uncheck the Include Crash Reporter in the project packaging settings so it won't end up in the build.

[Edstub207]

@tustanivsky Thanks for confirming.

Also thank you for reminding me RE: Windows Only - Is there a plan to expand beyond Windows (EG: Linux?)

[tustanivsky]

Also thank you for reminding me RE: Windows Only - Is there a plan to expand beyond Windows (EG: Linux?)

On Linux sentry-native takes care of capturing crashes without additional configuration. You may want to check https://github.com/EpicGames/UnrealEngine/pull/7976 to get a better idea of how we've ended up adding that checkbox for Windows specifically.

[tustanivsky]

Hey @Edstub207, as mentioned before on Linux sentry-native handles crash capturing out of the box without needing to configure Crash Reporter. Crashpad which native integration uses under the hood picks up a game log and dump file earlier compared to Crash Reporter and therefore their content could differ. However that shouldn't prevent you from getting a properly symbolicated call stack to diagnose the cause of the crash if Sentry has access to corresponding debug symbols. Those can be either uploaded to Sentry using the built-in plugin's tool or you can configure a custom symbol server. Apparently the first option doesn't work for you as mentioned in #329 (comment) so I wanted to ask whether you considered a second one?

[Edstub207]

@tustanivsky Sorry should have been clearer, we use a symbol server for Windows Clients and upload the Linux Server outside of the PostBuild.bat action that's within the plugin itself.

[tustanivsky]

@tustanivsky Sorry should have been clearer, we use a symbol server for Windows Clients and upload the Linux Server outside of the PostBuild.bat action that's within the plugin itself.

Thank you for clarifying.

So, having the about limitation of sentry-native (missing crash callstack in the game log) is there any other info lacking for the event captured by Sentry? I'm just trying to put all those bits together to understand if there is something we need to fix on plugin's side.