Configurable location for Crashpad storage
Closed this issue · 1 comments
Is your feature request related to a problem? Please describe.
CEF currently doesn't allow you to run two instances of the same application without these (partially) sharing Crashpad storage location. Crash dump storage location is currently configurable by having the process set the BREAKPAD_DUMP_LOCATION environment variable, but the crash metrics storage location is not.
Describe the solution you'd like
We'd like the BREAKPAD_DUMP_LOCATION solution extended to also cover crash metrics storage, either by using a shared base path variable or multiple variables. If there are other features unrelated to Crashpad that doesn't allow you to configure custom base paths for storage it'd be great to have a way of configuring these too.
Describe alternatives you've considered
We can't think of an alternative method to achieve the same result that doesn't require changing CEF.
We're currently only implementing CefCrashReporterClient::GetCrashMetricsLocation for Windows. The default in Chromium for non-Google Chrome-branded builds is to return false (which disables metrics collection here). We should probably just do that for CEF as well, since we don't do anything with these metrics in any case.