BTW the associated bug was closed by upstream presumptuously but there is a
linked pull request that actually seeks to fix the issue. Specifically:
https://github.com/lxqt/lxqt-session/pull/256
** Description changed:
- lxqt-session had multiple gigabytes RSS memory.
+ STEPS TO REPRODUCE
+ 0. P
** Changed in: lxqt-session (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/1823416
Title:
runaway high memory usage in lxqt-session
To manage notifications abo
** Changed in: lxqt
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823416
Title:
runaway high memory usage in lxqt-session
To manage notifications about this
** Bug watch added: github.com/lxqt/lxqt/issues #442
https://github.com/lxqt/lxqt/issues/442
** Also affects: lxqt via
https://github.com/lxqt/lxqt/issues/442
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "massif visualizer chart"
https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1823416/+attachment/5253280/+files/lxqt-session-massif.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
