https://bugs.kde.org/show_bug.cgi?id=496469
TraceyC <kde...@tlcnet.info> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|core |performance
--- Comment #142 from TraceyC <kde...@tlcnet.info> ---
We really do understand the frustration people have with long standing bugs
like this. It's frustrating for us as well when we can't reproduce something
and Just Fix It.
With that said, please keep discussion of this bug related to the bug itself.
Straying into tangents and trying to guess what other people are thinking only
clutters up the report and makes it more confusing.
To get this back on track, here are the details that stand out. The problem
occurs on:
- Single or multi-GPU systems
- Seen with GPUs: AMD, Nvidia, Intel
- A common cause is displays waking up / being added
Workaround:
Unplugging the HDMI / display cable and plugging it back in indeed causes the
memory to be released
Alternatively run
kwin_wayland --replace
What would be most helpful for us at this point is to get some performance data
during high memory usage. This will give us insight into which parts of the
code are causing the problem. If anyone wants to do this, you can use `perf`.
You can get `perf` from a package usually called something like `linux-tools`
from your distro. After you install that, run this while the memory leak is
happening:
```bash
sudo perf record -F 1000 -p $(pidof kwin_wayland) -g -- sleep 6
```
You can then view a report you can copy and paste. This will be generated based
on the `perf.data` file from the last step. Run this:
```
sudo perf report
```
Another thing that would be helpful for us is if someone could get us a
flamegraph of kwin_wayland while it's using a high amount of memory, if anyone
has set up the tools for that.
--
You are receiving this mail because:
You are watching all bug changes.
