mirror of https://github.com/chromium/crashpad.git synced 2024-12-28 15:50:26 +08:00

Go to file

Mark Mentovai 8297b19a5e Don’t attempt to do periodic tasks in a secondary crashpad_handler

76a67a37b1d0 adds crashpad_handler’s --monitor-self argument, which
results in a second crashpad_handler instance running out of the same
database as the initial crashpad_handler instance that it monitors. The
two handlers start at nearly the same time, and will initially be on
precisely the same schedule for periodic tasks such as scanning for new
reports to upload and pruning the database. This is an unnecessary
duplication of effort.

This adds a new --no-periodic-tasks argument to crashpad_handler. When
the first instance of crashpad_handler starts a second to monitor it, it
will use this argument, which prevents the second instance from
performing these tasks.

When --no-periodic-tasks is in effect, crashpad_handler will still be
able to upload crash reports that it knows about by virtue of having
written them itself, but it will not scan the database for other pending
reports to upload.

Bug: crashpad:143
Test: crashpad_util_test ThreadSafeVector.ThreadSafeVector
Change-Id: I7b249dd7b6d5782448d8071855818f986b98ab5a
Reviewed-on: https://chromium-review.googlesource.com/473827
Reviewed-by: Robert Sesek <rsesek@chromium.org>

2017-04-14 19:52:14 +00:00

build

handler: Add user extensibility stream call-out.

2017-04-11 19:06:00 +00:00

client

mac: Prevent the same report from being uploaded multiple times

2017-04-13 14:12:56 +00:00

compat

linux: Fix crashpad_util_test ScopedPtraceAttach.* with the Yama LSM

2017-04-07 21:28:59 +00:00

doc

designdoc: Add description of user data sources.