https://bugs.kde.org/show_bug.cgi?id=496469
kde.2ip0k@aihaiti.space changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kde.2ip0k@aihaiti.space
--- Comment #42 from kde.2ip0k@aihaiti.space ---
(In reply to Lech from comment #35)
> Trying to be helpful here:
> - are we all using optimus with the amd/intel GPU as the main one?
Intel iGPU and Nvidia dGPU with driver 565.77 in my case
> - do we all have the external monitor ports connected to the same GPU?
Using HDMI port that is connected to dGPU
> - are we all having this issue only when putting the laptop to sleep and
> waking it up?
I experience memory leaks in two scenarios:
1. After waking up from sleep
2. After disconnecting and reconnecting external monitors
Initially, I thought these scenarios were equivalent (both involving display
reconnection), but comment #37 and comment #40 suggest there might be different
underlying causes.
I can confirm the observation from comment #24: the frequency of display
repaints correlates with the rate of memory consumption, eventually using all
available RAM.
---
Regarding Case (2) (Display Freezing):
I've also experienced the image output freezing issue mentioned in the bug
description, but in my case it was specifically related to using the kzones
KWin script (https://github.com/gerritdevriese/kzones). After monitor
disconnection/reconnection while using this script:
- ~50% of cases: Moving windows causes complete image output freeze
- `kwin_wayland --replace` fails with `qt.qpa.xcb: could not connect to
display`
- Requires killing kwin_wayland via SSH and then SDDM appears
- ~50% of cases: Only the memory leak occurs
A potentially related issue was reported at
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12341#note_2657149,
describing both freezing and memory leaks after sleep/wake cycles.
While I am not sure to what extent the freezing behavior is related to the
memory leak and everyone is discussing mostly the memory leak, I'm including
this information since it was mentioned in the original bug description.
--
You are receiving this mail because:
You are watching all bug changes.
