Comment 4 for bug 1278780

On Mon, 22 Jun 2015, Steve Langasek wrote:
> The only part that should be running when not on wifi is the crash
> collection. We certainly *should* be running that when not on wifi; you
> don't get a second chance to run the kernel crash handler, and we want to
> know about crashes that only happen when not on wifi (including, possibly,
> crashes that happen /because/ you're not on wifi).

While that may be true, there has to be an option to switch off such crash
collection permanently or temporarily. This must not be enforced on the user,
which is the way it is right now, if I understood all this correctly. Not only
because some people might not feel comfortable with this informationbeing sent
before they can review it.

> The trouble is that, until the crash handler has finished consuming the core
> file from the kernel and exited, the original process is blocked. So the
> shell can't know that the process has died and move on until the crash
> handler has finished running. (The same is true on the desktop, it's just
> less impactful because the app is usually not full screen and blocking the UI
> at the time.)

Thanks for the explanation. To me, this is just all the more reason to have an
option to disable it, maybe only for a day or a couple. Imagine being somewhere
and urgently needing your phone which then hangs because some crash logs are
being collected? The app that crashed might not even be the one you urgently
need. Crash collection should, imho, not take precedence over the dialog to
accept a call as this is still the main functionaly of a phone, at least for
me.

Cheers,
Torsten