touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #25069
[Bug 1379296] Re: unity8-dash should be excluded from app lifecycle management
I think we need to put the dash between the background apps and the
foreground app, so that your foreground app doesn't die before the
(backgrounded) dash.
The problem is also that the unity8-dash job is respawning, as it's not
a "normal" app, so it won't wait until you focus it again to restart...
Although that might not be desirable in itself...
And then we need to reduce the mem usage in unity8-dash when people have
large music collections (like ogra!).
** Changed in: unity8 (Ubuntu)
Status: New => Triaged
** Changed in: unity8 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1379296
Title:
unity8-dash should be excluded from app lifecycle management
Status in “qtmir” package in Ubuntu:
New
Status in “unity8” package in Ubuntu:
Triaged
Bug description:
having a lot of apps open my unity8-dash gets contantly killed along
the apps if a certain OOM threshold is reached ... this appears like a
system crash of the UI (even though it is desired killing) from a user
perspective ...
checking the oom_score_adj values of all running apps i see that the
dash has the same high value as all other open foreground apps:
...
11 7960 oxide-renderer
11 7963 oxide-renderer
11 7988 oxide-renderer
300 6170 oxide-renderer
802 12514 unity8-dash
802 6088 webbrowser-app
802 6873 webapp-containe
802 7425 webapp-containe
802 7910 webapp-containe
(the full log can be found at http://paste.ubuntu.com/8526308/ ) given
that the dash is one part of our core UI it should be excluded from
app lifecycle management (keeping the same oom_score of 10 as unity8
does) so that only actual apps get killed on high memory pressure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1379296/+subscriptions
References