Increasing crash dump file size allowance for recurring crash

[LKCot]

Problem Statement

Hi All,

We are currently using Sentry Native in our application and have come across some limitations in investigating crashes with regards to the amount of information stored in the crash dump files due to the flags used in the minidump settings in Sentry.

I would like to propose the following feature:

When a user experiences multiple crashes with the same perceived root cause (based on the stack trace), Sentry will switch on more MiniDump flags, so that the next time the crash happens a mini dump with more information is generated. The specific thresholds and flags could also possibly be configurable via the API. Another option is that Sentry just detects multiple crashes within a specific time frame (regardless of root cause), and increases mini dump information.

In relation to this, the maximum upload size of dump files is increased to be larger than 100MB, to allow for the larger minidump files that would be generated.

Thanks,

Liam

Solution Brainstorm

No response

Product Area

APIs

[linear]

ENG-6300

NATIVE-158

NATIVE-157

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[mujacica]

Hello Liam!

We are currently working on multiple features you mentioned here. The main unblocker for accepting the larger Minidumps is the backend infrastructure - and as soon as the work there is done - it should allow us to accept larger Attachments/Minidumps. I will follow-up here with the ticket you could use to track progress there.

Amir