Try a heap profiler. The problem with high memory usage is that it's
often just indefinitely bloat and not a permanent 'leak'. This means the
program still has enough smarts to free it all on shutdown and no leak
checker will tell you what the problem was. But while it's running it's
still too big.
I observed this with x+o, deb based.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659255
Title:
memory leak
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
curious - is this zesty? or xenial+overlay?
also, is this debs or snaps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659255
Title:
memory leak
To manage notifications about this bug go to:
https
** Changed in: unity8 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659255
Title:
memory leak
To manage notifications about this bug go to:
https://bugs.laun
