Crashpad minidump upload only works once when the database is created

[Flo Loferer]

Hi folks,

not sure if this is the right spot. Please feel free to redirect me to a user group or similar.
I'm trying to integrate crashpad into our app but I'm having trouble with the automatic upload.
I can only get it to work with the very first crash.

For all subsequent crashes, I'm not seeing any network activity and my crash server service sentry.io doesn't show any activity...

Automatic uploads are enabled in the database settings.

Not sure if this is related, but I'm getting this error on every app launch logged to the console:

nw_path_close_fd Failed to close guarded necp fd 9 [9: Bad file descriptor]

I'm rather desperate as I really don't know what else I could try...
I built crashpad from source (macOS 10.13) as well as the depot tools and mini_chromium.

Thanks and best,

Flo

[Scott Graham]

Hi,

I'm not too familiar with Mac, but one common thing that comes up is that uploads are throttled by default in https://cs.chromium.org/chromium/src/third_party/crashpad/crashpad/handler/crash_report_upload_thread.cc?&l=165.

Perhaps try running with --no-rate-limit https://cs.chromium.org/chromium/src/third_party/crashpad/crashpad/handler/handler_main.cc?sq=package:chromium&l=571 to see if you see second and subsequent uploads then?

--
You received this message because you are subscribed to the Google Groups "Crashpad-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crashpad-dev...@chromium.org.
To post to this group, send email to crashp...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/crashpad-dev/f3cbcc47-53ed-4407-aab3-6b3cc89e6844%40chromium.org.

[florian...@gmx.de]

Thanks Scott!!

How could I miss that?? That works!!
What happens when this option is not set and several crashes appear within one hour?
Are they sent in one batch later on or are they just discarded??

[Scott Graham]

I'm glad that's all it was.

The default behaviour is that all the crashes are saved locally, but they'll never be uploaded (only 1/hour). The idea is that it's likely to be the same crash if it's happening frequently, but it's a pretty weak heuristic.

Chrome has a UI surface that allows the user to manually trigger an upload for one of the not-uploaded crashes, which is done by calling RequestUpload() on the database's crash, but there's nothing more automatic than that.

We'd like to write something smarter for throttling, but it just hasn't happened yet unfortunately. https://bugs.chromium.org/p/crashpad/issues/detail?id=23

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/crashpad-dev/3213771e-9283-4702-8f9a-7ccbb08baf0b%40chromium.org.