[Desktop-packages] [Bug 1473562] Re: Too many crash files kill the device
This bug was fixed in the package apport - 2.17.2-0ubuntu1.2
---
apport (2.17.2-0ubuntu1.2) vivid-proposed; urgency=medium
* apport-noui.upstart: Utilize watershed to only launch one instance of
whoopsie-upload-all at a time. (LP: #1473562)
* apport-noui: Depend on watershed.
-- Brian Murray Fri, 24 Jul 2015 15:27:31 -0700
** Changed in: apport (Ubuntu Vivid)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1473562
Title:
Too many crash files kill the device
Status in Canonical System Image:
Fix Committed
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Vivid:
Fix Released
Bug description:
Tested on krillin.
TEST CASE:
1. adb shell to the phone and create a crash file
$ sh -c 'kill -SEGV $$'
2. Now create dozens
$ for n in $(seq 50); do ln /var/crash/_bin_dash.32011.crash
/var/crash/_bin_dash_${n}.32011.crash; done
3. Remove any "upload" and "uploaded" files that have been created and reboot
$ sudo rm /var/crash/*upload* && sudo reboot
ACTUAL RESULT
Lot of whoopsie-upload-all and apport processes are created on boot, consume
all the resources of the system and make the phone unbootable or partially
functional. OOM killer kills random system tasks such as upstart. Depending on
the processes killed, the phone hangs on boot, reboots, dash doesn't come up...
The number of crashes in this test is a bit excessive but we can
imagine a scenario where a dozen of crash files are not uploaded
because the phone is on cellular data, and uploads everything when it
connects to wifi, disabling the user session.
A way to recover is to go into recovery and clean /var/crash.
EXPECTED RESULT
crash uploads are serialized and can be uploaded only one at a time
If system resources are already low, the crash file is not uploaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473562/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473562] Re: Too many crash files kill the device
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1473562
Title:
Too many crash files kill the device
Status in Canonical System Image:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Vivid:
Fix Released
Bug description:
Tested on krillin.
TEST CASE:
1. adb shell to the phone and create a crash file
$ sh -c 'kill -SEGV $$'
2. Now create dozens
$ for n in $(seq 50); do ln /var/crash/_bin_dash.32011.crash
/var/crash/_bin_dash_${n}.32011.crash; done
3. Remove any "upload" and "uploaded" files that have been created and reboot
$ sudo rm /var/crash/*upload* && sudo reboot
ACTUAL RESULT
Lot of whoopsie-upload-all and apport processes are created on boot, consume
all the resources of the system and make the phone unbootable or partially
functional. OOM killer kills random system tasks such as upstart. Depending on
the processes killed, the phone hangs on boot, reboots, dash doesn't come up...
The number of crashes in this test is a bit excessive but we can
imagine a scenario where a dozen of crash files are not uploaded
because the phone is on cellular data, and uploads everything when it
connects to wifi, disabling the user session.
A way to recover is to go into recovery and clean /var/crash.
EXPECTED RESULT
crash uploads are serialized and can be uploaded only one at a time
If system resources are already low, the crash file is not uploaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473562/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473562] Re: Too many crash files kill the device
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1473562
Title:
Too many crash files kill the device
Status in Canonical System Image:
New
Status in apport package in Ubuntu:
New
Bug description:
Tested on krillin.
TEST CASE:
1. adb shell to the phone and create a crash file
$ sh -c 'kill -SEGV $$'
2. Now create dozens
$ for n in $(seq 50); do ln /var/crash/_bin_dash.32011.crash
/var/crash/_bin_dash_${n}.32011.crash; done
3. Remove any "upload" and "uploaded" files that have been created and reboot
$ sudo rm /var/crash/*upload* && sudo reboot
ACTUAL RESULT
Lot of whoopsie-upload-all and apport processes are created on boot, consume
all the resources of the system and make the phone unbootable or partially
functional. OOM killer kills random system tasks such as upstart. Depending on
the processes killed, the phone hangs on boot, reboots, dash doesn't come up...
The number of crashes in this test is a bit excessive but we can
imagine a scenario where a dozen of crash files are not uploaded
because the phone is on cellular data, and uploads everything when it
connects to wifi, disabling the user session.
A way to recover is to go into recovery and clean /var/crash.
EXPECTED RESULT
crash uploads are serialized and can be uploaded only one at a time
If system resources are already low, the crash file is not uploaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473562/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1473562] Re: Too many crash files kill the device
I've uploaded this to the vivid proposed queue for review by the SRU
team now.
** Also affects: apport (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Released
** Changed in: apport (Ubuntu Vivid)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: apport (Ubuntu Vivid)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1473562
Title:
Too many crash files kill the device
Status in Canonical System Image:
Confirmed
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Vivid:
In Progress
Bug description:
Tested on krillin.
TEST CASE:
1. adb shell to the phone and create a crash file
$ sh -c 'kill -SEGV $$'
2. Now create dozens
$ for n in $(seq 50); do ln /var/crash/_bin_dash.32011.crash
/var/crash/_bin_dash_${n}.32011.crash; done
3. Remove any "upload" and "uploaded" files that have been created and reboot
$ sudo rm /var/crash/*upload* && sudo reboot
ACTUAL RESULT
Lot of whoopsie-upload-all and apport processes are created on boot, consume
all the resources of the system and make the phone unbootable or partially
functional. OOM killer kills random system tasks such as upstart. Depending on
the processes killed, the phone hangs on boot, reboots, dash doesn't come up...
The number of crashes in this test is a bit excessive but we can
imagine a scenario where a dozen of crash files are not uploaded
because the phone is on cellular data, and uploads everything when it
connects to wifi, disabling the user session.
A way to recover is to go into recovery and clean /var/crash.
EXPECTED RESULT
crash uploads are serialized and can be uploaded only one at a time
If system resources are already low, the crash file is not uploaded.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473562/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
