OOM score for apps waiting on content hub should be adjusted
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
Confirmed
|
High
|
Bill Filler | ||
| Ubuntu Application Launcher |
New
|
High
|
Unassigned | ||
| content-hub (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
| qtmir (Ubuntu) |
Confirmed
|
High
|
Unassigned | ||
Bug Description
I happens that the app gets killed by OOM while it is being put into background importing something from the content hub. I think apps waiting on something from the content hub should have a better OOM score to make it less likely. Even if the app is restarted automatically after picking content from the hub, the transfer will fail because it lost the pointer to the transfer object.
On bq, if apps have some data in it, this becomes really a problem. For example it's close to impossible to add a new contact to telegram if there are many apps openened, because Telegram seems to have a higher OOM score than most other things, and it gets killed while the user picks some contact from the address book. The user has to manually close all other apps, sometimes even reboot before being able to do that again.
Related branches
- system-apps-ci-bot: Needs Fixing (continuous-integration)
- PS Jenkins bot: Needs Fixing (continuous-integration)
- Ubuntu Phablet Team: Pending requested
-
Diff: 1425 lines (+1032/-9)25 files modifiedCMakeLists.txt (+4/-2)
debian/content-hub.install (+1/-0)
debian/control (+2/-0)
import/Ubuntu/Content/contenthub.h (+1/-0)
include/com/ubuntu/content/transfer.h (+4/-0)
src/CMakeLists.txt (+2/-1)
src/com/ubuntu/applicationmanager/application_manager.h (+14/-0)
src/com/ubuntu/content/CMakeLists.txt (+3/-0)
src/com/ubuntu/content/detail/app_manager.cpp (+29/-1)
src/com/ubuntu/content/detail/app_manager.h (+2/-0)
src/com/ubuntu/content/detail/com.ubuntu.content.Service.xml (+4/-0)
src/com/ubuntu/content/detail/com.ubuntu.content.Transfer.xml (+9/-0)
src/com/ubuntu/content/detail/mir-helper.cpp (+235/-0)
src/com/ubuntu/content/detail/mir-helper.h (+69/-0)
src/com/ubuntu/content/detail/service.cpp (+54/-4)
src/com/ubuntu/content/detail/service.h (+5/-1)
src/com/ubuntu/content/detail/transfer.cpp (+38/-0)
src/com/ubuntu/content/detail/transfer.h (+7/-0)
src/com/ubuntu/content/transfer.cpp (+10/-0)
src/com/ubuntu/content/transfer_p.h (+19/-0)
src/helper/CMakeLists.txt (+61/-0)
src/helper/exec-tool.c (+222/-0)
src/helper/exec-tool.cpp (+107/-0)
src/helper/mir-connection-demangler.c (+126/-0)
tests/acceptance-tests/app_manager_mock.h (+4/-0)
| Changed in qtmir: | |
| importance: | Undecided → Critical |
| tags: | added: bq |
| description: | updated |
| Changed in content-hub: | |
| importance: | Undecided → Critical |
| description: | updated |
| Changed in canonical-devices-system-image: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
| assignee: | nobody → kevin gunn (kgunn72) |
| kevin gunn (kgunn72) wrote | #1 |
| Changed in content-hub: | |
| status: | New → Confirmed |
| assignee: | nobody → Ken VanDine (ken-vandine) |
| Changed in canonical-devices-system-image: | |
| importance: | Critical → High |
| Changed in qtmir: | |
| importance: | Critical → High |
| Changed in content-hub: | |
| importance: | Critical → High |
| Changed in ubuntu-app-launch: | |
| importance: | Undecided → High |
| affects: | content-hub → content-hub (Ubuntu) |
| Michael Zanetti (mzanetti) wrote | #2 |
| Changed in canonical-devices-system-image: | |
| assignee: | kevin gunn (kgunn72) → Bill Filler (bfiller) |
| Changed in canonical-devices-system-image: | |
| milestone: | none → backlog |
| Changed in qtmir: | |
| status: | New → Confirmed |
| affects: | qtmir → qtmir (Ubuntu) |
| Changed in content-hub (Ubuntu): | |
| assignee: | Ken VanDine (ken-vandine) → nobody |
based on some discussion this morning in the unity8 sprint planning.
for the unity8 team we can only approach this with a short-term hack (potentially specifically for the telegram/contacts case) as content hub isn't relying on the trusted session mechanism, this would make it a more proper solution.
this bug will need to remain open for content hub to rely on trusted session. And there will still need to be some discussion around potential OOM scoring adjustments.