Philipp Hofmann

@bruno-garcia and @bitsandfoxes, I think you both mentioned we would need this for Unity, and this issue could block you. Is this true?

@m-kuhn, yes, please share it with us. That would be lovely.

@Swatinem and @armcknight , can you maybe help us here? We allocate a struct with a maximum of 100 stack entries before suspending the threads. Here we are walking the...

Thanks, @Swatinem, for your reply. I thought so, but worth a shot. @brustolin, I think we could increase the value to 256 then.

Do you do anything special when you exceed the maximum, like adding a special entry or making sure you cut from the bottom or top, or do you just ignore...

We also write stacktrace to disk when we crash, but this one we use when not crashing. So for App Hangs and in the future when calling captureMessage or captureError....

For most SentryCrash monitors we use `SentryCrashSC_STACK_OVERFLOW_THRESHOLD` https://github.com/getsentry/sentry-cocoa/blob/e65226c90c1bb83ab1c40483c8e310d686e1f11f/Sources/SentryCrash/Recording/Tools/SentryCrashStackCursor.h#L42 and for some others we use `MAX_STACKTRACE_LENGTH` https://github.com/getsentry/sentry-cocoa/blob/e65226c90c1bb83ab1c40483c8e310d686e1f11f/Sources/SentryCrash/Recording/Tools/SentryCrashStackCursor_MachineContext.h#L34 We advance the cursor while writing a report to disk in here https://github.com/getsentry/sentry-cocoa/blob/e65226c90c1bb83ab1c40483c8e310d686e1f11f/Sources/SentryCrash/Recording/SentryCrashReport.c#L816-L850 So...

Just to be safe, we could only increase the stacktrace size for App Hangs to avoid possible side effects.

Hey @christhegrand, sorry for abandoning the issue. Do you still experience the problem? Did you find a workaround?

If @krystofwoldrich agrees, I'm happy to close this issue.