The existing upstart job for whoopsie-upload-all is designed to ensure
that only one whoopsie-upload-all process takes care of the upload
processing on boot. However, it's true that if there are multiple crash
files in the directory, separate whoopsie-upload-all processes will be
/spawned/ for each crash file, and they will be spawned in parallel. So
while the current behavior is responsible with its use of CPU time, it's
less than ideal with memory usage; each instance of the whoopsie-upload-
all python script uses about 50MB (on amd64), and while some of that is
shared libraries, the stack usage will add up.
I suggest that a simple fix for this would be to change the apport-noui
upstart job to wrap the calls to whoopsie-upload-all with
/lib/udev/watershed. This would limit us to one running whoopsie-
upload-all process at a time; there would be multiple watershed
processes, but those processes take up much less memory (roughly 300kb
each).
Brian, can you look at adding watershed to this job to see if that
addresses the problems for the phone?
** Changed in: apport (Ubuntu)
Importance: Undecided => High
** Changed in: apport (Ubuntu)
Status: New => Triaged
** Changed in: apport (Ubuntu)
Assignee: Steve Langasek (vorlon) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473562
Title:
Too many crash files kill the device
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473562/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
