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
I observed this with x+o, deb based.
--
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/1659255
Title:
memory leak
Status in unity8 package in Ubuntu:
Triaged
Bug
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
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1659255
Title:
memory leak
Status in unity8
** Changed in: unity8 (Ubuntu)
Status: New => Triaged
--
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/1659255
Title:
memory leak
Status in unity8 package in Ubuntu:
4 matches
Mail list logo
