No report sent at all when kernel/Apport lacks memory for core dump
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Apport |
Confirmed
|
Medium
|
Unassigned | ||
| Daisy |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
1. Trigger a crash for which the kernel does not have enough memory to generate a core dump, or Apport does not have enough memory to load it. For example, a Compiz crash in a VM.
What happens: An error message appears, "Your system does not have enough memory to process this crash report."
What should happen: The normal error alert appears, and a minimal error report is sent containing everything except the core dump.
This wouldn't have made sense when Launchpad Bugs was the only destination for crash reports. But with errors.ubuntu.com, it's interesting to know the number of crashes for accounting purposes. (And if the proportion without core dumps gets sufficiently large, we'll know it's time to change something so that more cores get dumped.)
| summary: |
- No report sent at all when kernel lacks memory for core dump + No report sent at all when kernel/Apport lacks memory for core dump |
| Martin Pitt (pitti) wrote | #1 |
| Changed in apport: | |
| status: | New → Incomplete |
| Matthew Paul Thomas (mpt) wrote | #2 |
| Changed in apport: | |
| status: | Incomplete → New |
| tags: | added: whoopsie-daisy |
| Changed in daisy: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Changed in apport: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
These reports would have no strack trace, no duplicate signature, etc., i. e. nothing that would identify the particular crash in any way; we would just know "foo has crashed with SIGBUS". Woudl that actually be useful for errors.u.c? In which bucket would these be put in?