lxqt-session allocates memory for process output never read
Bug #1823416 reported by
Kevin Turner
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| LXQt |
Fix Released
|
Unknown
|
|||
| lxqt-session (Ubuntu) |
Fix Released
|
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
Revision history for this message
| Kevin Turner (keturn) wrote | #1 |
Revision history for this message
| Kevin Turner (keturn) wrote | #2 |
| Changed in lxqt: | |
| status: | Unknown → Fix Released |
| Changed in lxqt-session (Ubuntu): | |
| status: | New → Triaged |
Revision history for this message
| ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote | #3 |
| description: | updated |
| summary: |
- runaway high memory usage in lxqt-session + lxqt-session allocates memory for process output never read |
| tags: | added: disco lubuntu |
| Changed in lxqt-session (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
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:/