ubuntu-phone team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

On Mon, Jun 22, 2015 at 02:48:01PM +0200, Oliver Grawert wrote:
> seems that whoopsie refuses to send your report because you are not on
> wifi, perhaps it should check for this earlier and not even run the
> collection, not sure ... 

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).

On Mon, Jun 22, 2015 at 02:19:10PM +0100, Alan Pope wrote:

> Also, related to the discussion:-
> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1278780

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.)

We have already taken steps to minimize the amount of processing done on the
core file as part of the apport crash handler, in favor of post-processing
the crash file from a queue.  It's not clear what further optimization of
the crash handler is possible.

On Mon, Jun 22, 2015 at 02:39:04PM +0200, Oliver Grawert wrote:
> hi,
> Am Montag, den 22.06.2015, 14:28 +0200 schrieb Marco F:

> > Who decided that collection of debug information is the task with
> > highest priority on a phone which wishes to be used by the public?

> i think it already runs at a very low prio (obviously still to high for
> the phone though ... )

Running it with a low priority would NOT improve the user experience.  It
would just cause the app to hang longer in an unkillable, memory-consuming
state.