lxqt-session allocates memory for process output never read

Bug #1823416 reported by Kevin Turner on 2019-04-05
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LXQt
Fix Released
Unknown
lxqt-session (Ubuntu)
Undecided
Unassigned

Bug Description

STEPS TO REPRODUCE
 0. Prepare a 100MB file, e.g. `dd if=/dev/urandom of=foo bs=1MB count=1`
 1. Create a script to read the above file to standard output, i.e. `cat foo`
 2. Monitor lxqt-session memory usage, using qps or `ps -C lxqt-session -F` (watch RSS)
 3. Run the script through lxqt-panel or lxqt-runner

EXPECTED RESULTS
Memory is not allocated for the script.

ACTUAL RESULTS
Memory is allocated for the script and stays allocated.

AFFECTED VERSIONS
0.13.0-0ubuntu2
0.14.1-0ubuntu1

Kevin Turner (keturn) wrote :
Kevin Turner (keturn) wrote :
Changed in lxqt:
status: Unknown → Fix Released
Walter Lapchynski (wxl) on 2019-04-07
Changed in lxqt-session (Ubuntu):
status: New → Triaged
Walter Lapchynski (wxl) wrote :

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: updated
summary: - runaway high memory usage in lxqt-session
+ lxqt-session allocates memory for process output never read
tags: added: disco lubuntu
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.