touch-packages 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.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1278780

Title:
  apport takes too long to write crash report, appears to lock up phone

Status in Apport crash detection/reporting:
  Confirmed
Status in apport package in Ubuntu:
  Triaged

Bug description:
  I can trigger a crash easily on my phone via bug 1262711. Other bugs
  are available.

  When that happens my phone appears to freeze. I am unable to do
  anything for approximately 1 to 1.5 minutes. As a user my initial gut
  reaction is to reboot the phone, thus losing the crash report, and
  wasting my time.

  Having the phone lock up for 1.5 minutes is a terrible user
  experience. Can we fix/mitigate/workaround that?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.13.2-0ubuntu2
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: armhf
  CrashReports:
   664:32011:110:10083:2014-02-10 15:41:18.152893384 +0000:2014-02-10 15:11:09.169231740 +0000:/var/crash/_usr_lib_arm-linux-gnueabihf_upstart-app-launch_desktop-hook.32011.crash
   640:0:110:1681527:2014-02-10 15:12:10.985193887 +0000:2014-02-10 15:12:05.639489630 +0000:/var/crash/_usr_bin_powerd.0.crash
   640:0:110:21384:2014-02-11 07:58:44.876281991 +0000:2014-02-11 07:58:44.876281991 +0000:/var/crash/_usr_sbin_system-image-dbus.0.crash
   640:32011:110:17122318:2014-02-11 09:19:49.915478726 +0000:2014-02-11 09:18:20.850439824 +0000:/var/crash/_usr_bin_unity8.32011.crash
  Date: Tue Feb 11 09:20:15 2014
  InstallationDate: Installed on 2014-02-11 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140211)
  PackageArchitecture: all
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1278780/+subscriptions