https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #124 from Colin Gauvin ---
(In reply to Neod from comment #123)
> The bug may relate to multi-GPU copy mode.
> I changed the "display NV DDS Function" settings in BIOS from "MsHybrid" to
> "dGPU only". The problem does not happen anymore.
>
https://bugs.kde.org/show_bug.cgi?id=496469
Neod changed:
What|Removed |Added
Version Fixed In|6.2.5 |
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=496469
Neod changed:
What|Removed |Added
CC||neodzc2...@126.com
--- Comment #123 from Neod ---
The b
https://bugs.kde.org/show_bug.cgi?id=496469
Mike Goodwin changed:
What|Removed |Added
CC||m...@mgoodwin.net
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=496469
cubercsl <2014cai...@gmail.com> changed:
What|Removed |Added
CC||2014cai...@gmail.com
--
You a
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #122 from barra ---
(In reply to Evert Vorster from comment #121)
> (In reply to barra from comment #120)
> > (In reply to Evert Vorster from comment #117)
> > > (In reply to barra from comment #115)
> > > > nope, i cannot downgrade, it will
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #121 from Evert Vorster ---
(In reply to barra from comment #120)
> (In reply to Evert Vorster from comment #117)
> > (In reply to barra from comment #115)
> > > nope, i cannot downgrade, it will just reject
> > > ```
> > > /usr/lib/libnvidi
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #120 from barra ---
(In reply to Evert Vorster from comment #117)
> (In reply to barra from comment #115)
> > nope, i cannot downgrade, it will just reject
> > ```
> > /usr/lib/libnvidia-egl-gbm.so exists in both 'nvidia-utils' and 'egl-gbm'
https://bugs.kde.org/show_bug.cgi?id=496469
Tanel Tammik changed:
What|Removed |Added
CC||m...@keevitaja.com
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #112 from Evert Vorster ---
Unfortunately for me, it was leaking even without a suspend/resume cycle.
I have recently updated the firmware on my external monitor, and it fixed a
some other issues I was having, so I will test again with the
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #104 from Chan ---
(In reply to Evert Vorster from comment #101)
> I spoke too soon, after a suspend-resume cycle, I could see the memory
> counting up in kwin_wayland just sitting there, with nothing happening on
> screen.
>
> So, false a
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #119 from Zamundaaa ---
It only happens with NVidia, and only with newer driver versions. That doesn't
necessarily mean it's a driver bug, but it's not unlikely, and we're not
getting anywhere here either way.
(In reply to barra from commen
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #118 from Evert Vorster ---
(In reply to barra from comment #116)
> Shouldn't we file a bug on nvidia repo?
First, we have to figure out what the issue is. Other window managers does not
seem to have this problem, so the signs are pointing
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #117 from Evert Vorster ---
(In reply to barra from comment #115)
> nope, i cannot downgrade, it will just reject
> ```
> /usr/lib/libnvidia-egl-gbm.so exists in both 'nvidia-utils' and 'egl-gbm'
> /usr/lib/libnvidia-egl-gbm.so.1 exists in b
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #116 from barra ---
Shouldn't we file a bug on nvidia repo?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #115 from barra ---
nope, i cannot downgrade, it will just reject
```
/usr/lib/libnvidia-egl-gbm.so exists in both 'nvidia-utils' and 'egl-gbm'
/usr/lib/libnvidia-egl-gbm.so.1 exists in both 'nvidia-utils' and 'egl-gbm'
/usr/share/egl/egl_ex
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #114 from barra ---
> i noticed the bug only triggers once external monitor is unplugged then
> replugged in. Then kwin will start consuming more and more memory, about
> 100mb per minute here, as long as the external monitor screen keeps ge
https://bugs.kde.org/show_bug.cgi?id=496469
barra changed:
What|Removed |Added
CC||ba...@duck.com
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #113 from Evert Vorster ---
Just confirmed that this issue is still present in the 570 version of the
nvidia drivers, even after the monitor's firmware update, and HDR on.
--
You are receiving this mail because:
You are watching all bug ch
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #111 from Tanel Tammik ---
(In reply to charly ghislain from comment #106)
>
> i noticed the bug only triggers once external monitor is unplugged then
> replugged in. Then kwin will start consuming more and more memory, about
> 100mb per mi
https://bugs.kde.org/show_bug.cgi?id=496469
TraceyC changed:
What|Removed |Added
CC||kde...@tlcnet.info
Keywords|
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #110 from Miroslav Jarý ---
I can also confirm that switching to nvidia driver version 550.144.03 memory
leaks seems to be gone.
After a bit of googling I found this on nvidia forums:
https://forums.developer.nvidia.com/t/extreme-growing-me
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #106 from charly ghislain ---
i noticed the bug only triggers once external monitor is unplugged then
replugged in. Then kwin will start consuming more and more memory, about
100mb per minute here, as long as the external monitor screen keep
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #109 from Evert Vorster ---
Been running for a few hours now, and with nVidia 550.144 kwin_wayland's memory
usage is absolutely stable.
One notable code path that is not in the 550.144 is HDR, which I am kind of
missing.
Looking through t
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #108 from el...@seznam.cz ---
Indeed, I remember that NVIDIA 550 was the last one that worked for me.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #107 from Evert Vorster ---
Downgrading to nVidia 550.144 dkms in Arch definitely cured the issue for me.
System has gone through sleep cycles, had it's external monitor unplugged and
plugged back in again.
kwin_wayland is sitting at 377Mb
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #105 from Evert Vorster ---
(In reply to Chan from comment #104)
> (In reply to Evert Vorster from comment #101)
> Can you check if this issue occurs to you if on the 6.6 LTS kernel?
I'm a bit reluctant to run such an old kernel, my hardware
https://bugs.kde.org/show_bug.cgi?id=496469
Miroslav Jarý changed:
What|Removed |Added
Version|6.3.2 |6.3.4
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #103 from LucasGGamerM ---
In case anyone was wondering, 6.3.4 did not fix this issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496469
Jarrard changed:
What|Removed |Added
CC||jarr...@proton.me
--- Comment #102 from Jarrard ---
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #100 from Evert Vorster ---
For what it's worth, when using the 6.14 kernel this issue seems to be gone.
I'm currently running linux-mainline on Arch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #101 from Evert Vorster ---
I spoke too soon, after a suspend-resume cycle, I could see the memory counting
up in kwin_wayland just sitting there, with nothing happening on screen.
So, false alarm, 6.14 kernel does not, in fact, cure this
https://bugs.kde.org/show_bug.cgi?id=496469
kde.2ip0k@aihaiti.space changed:
What|Removed |Added
CC|kde.2ip0k@aihaiti.space |
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #98 from Evert Vorster ---
(In reply to righn from comment #95)
> (In reply to Evert Vorster from comment #94)
> > To add another data point for people who are looking into this one...
> > When connecting to the external monitor through a U
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #67 from Bráulio Barros de Oliveira ---
(In reply to Chan from comment #62)
> Is anyone here facing this issue while running the 6.6 LTS kernel? I somehow
> don't face this problem when I am running the 6.6 LTS kernel. I have run the
> same
https://bugs.kde.org/show_bug.cgi?id=496469
Alexander Kernozhitsky changed:
What|Removed |Added
CC||sh200...@mail.ru
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #85 from JPdxd ---
ok, for my setup, just ftr the external monitor is 1920*1080 and the rate of
increase (measured just with htop) is about 4M per second while scrolling this
page up/down fast (sometimes it is 6M but mostly it is 4M).
Idk
https://bugs.kde.org/show_bug.cgi?id=496469
Zamundaaa changed:
What|Removed |Added
CC||filipembed...@gmail.com
--- Comment #97 from Zamund
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #99 from Bráulio Barros de Oliveira ---
(In reply to tmpod from comment #78)
> Created attachment 179739 [details]
> signature.asc
>
> Promising... Which nvidia driver version are you on?
latest from Arch, 570.133.07,
https://archlinux.org
https://bugs.kde.org/show_bug.cgi?id=496469
Nick H changed:
What|Removed |Added
CC||kror...@gmail.com
--- Comment #96 from Nick H ---
SUM
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #95 from ri...@outlook.com ---
(In reply to Evert Vorster from comment #94)
> To add another data point for people who are looking into this one...
> When connecting to the external monitor through a USB-C to DisplayPort
> adapter, the issue
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #94 from Evert Vorster ---
To add another data point for people who are looking into this one...
When connecting to the external monitor through a USB-C to DisplayPort adapter,
the issue is not present, so it would seem to be localized only
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #93 from JPdxd ---
I did, but couldn't find what the issue is (skill issue here) I'm attaching the
heaptrack here, note the reserved memory grows, but the actual issue at least
for me is the shared memory buffer, and it only grows if there i
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #91 from postix ---
Has anyone tried to check with Hotspot [1], where the memory is being allocated
over time in kwin_wayland to get a hint?
[1] https://github.com/KDAB/hotspot
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #92 from postix ---
Sorry, I meant heaptrack: https://github.com/KDE/heaptrack
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496469
Evert Vorster changed:
What|Removed |Added
CC||evors...@protonmail.com
--- Comment #90 from Ev
https://bugs.kde.org/show_bug.cgi?id=496469
Colin Gauvin changed:
What|Removed |Added
CC||co...@gauvin.id
--- Comment #89 from Colin Gauvi
https://bugs.kde.org/show_bug.cgi?id=496469
Mateus Mercer changed:
What|Removed |Added
CC||accou...@matbm.net
--- Comment #88 from Mateus
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #87 from JPdxd ---
not sure how can be related, but after setting
KWIN_DRM_DISABLE_TRIPLE_BUFFERING=true
and loging out and in again, it seems a little bit more stable in terms of
shared memory
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #86 from JPdxd ---
Regarding toggling fullscreen, For me it increases SHR in 2M each event, and of
course there is a slight increase on CPU on the threads tagged with HDMI-A-1.
For now my workaround is to periodically switch the KVM to ano
https://bugs.kde.org/show_bug.cgi?id=496469
JPdxd changed:
What|Removed |Added
CC||jp.mn...@gmail.com
--- Comment #84 from JPdxd ---
For
https://bugs.kde.org/show_bug.cgi?id=496469
haventhef...@gmail.com changed:
What|Removed |Added
CC||haventhef...@gmail.com
--- Comment #83
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #82 from Miroslav Jarý ---
After a bit of testing, it seems that in this report there are many separate
issues, with similar symptoms - memory leak.
Some people report that replugging the monitors temporarily resolves the issue,
but I canno
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #81 from tmpod ---
I was replying to Bráulio, but more info is always good :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #80 from Vlad Zabotinsky ---
(In reply to righn from comment #74)
> (In reply to Vlad Zabotinsky from comment #73)
> > Any updates on this issue? Maybe any workaround? Kinda bad that i need to
> > unplug my monitor 3-6 times a day. If any in
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #79 from tmpod ---
> Created attachment 179739
> signature.asc
Oops, forgot you shouldn't reply with signed emails on bugzilla...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #78 from tmpod ---
Promising... Which nvidia driver version are you on?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #76 from Bráulio Barros de Oliveira ---
the issue seems gone with Linux 6.14 from Archlinux core-testing.
`kwin_wayland` RSS around 800mb, with 2 screens connected to the AMD iGPU and 1
to a NVIDIA 4060ti
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #77 from Bráulio Barros de Oliveira ---
the problem seems gone with Linux 6.14 from Archlinux core-testing.
kwin_wayland RSS stable ~800mb, with 2 4k screens connected to AMD iGPU and 1
4k screen to NVIDIA 4060ti
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #75 from Lech ---
(In reply to righn from comment #74)
> (In reply to Vlad Zabotinsky from comment #73)
> > Any updates on this issue? Maybe any workaround? Kinda bad that i need to
> > unplug my monitor 3-6 times a day. If any info is neede
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #74 from ri...@outlook.com ---
(In reply to Vlad Zabotinsky from comment #73)
> Any updates on this issue? Maybe any workaround? Kinda bad that i need to
> unplug my monitor 3-6 times a day. If any info is needed to understand
> problems caus
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #73 from Vlad Zabotinsky ---
Any updates on this issue? Maybe any workaround? Kinda bad that i need to
unplug my monitor 3-6 times a day. If any info is needed to understand problems
cause, provide me guide how to get this requiered info, so
https://bugs.kde.org/show_bug.cgi?id=496469
Jerzy Kołosowski changed:
What|Removed |Added
CC||k...@jkolo.pl
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #72 from LucasGGamerM ---
(In reply to LucasGGamerM from comment #71)
> I have noticed something weird about this bug. After unplugging and plugging
> my monitors back in, kwin only happens to leak memory (for me) when moving
> the mouse on
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #71 from LucasGGamerM ---
I have noticed something weird about this bug. After unplugging and plugging my
monitors back in, kwin only happens to leak memory (for me) when moving the
mouse on a monitor directly connected to the nvidia gpu, a
https://bugs.kde.org/show_bug.cgi?id=496469
LucasGGamerM changed:
What|Removed |Added
OS|All |Linux
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=496469
LucasGGamerM changed:
What|Removed |Added
OS|Linux |All
CC|
https://bugs.kde.org/show_bug.cgi?id=496469
Shastao changed:
What|Removed |Added
CC||shas...@gmail.com
--- Comment #70 from Shastao ---
F
https://bugs.kde.org/show_bug.cgi?id=496469
radimir.caci...@gmail.com changed:
What|Removed |Added
CC||radimir.caci...@gmail.com
--- Commen
https://bugs.kde.org/show_bug.cgi?id=496469
Matheus Castanho changed:
What|Removed |Added
CC||mscasta...@gmail.com
--- Comment #68 from Ma
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #66 from Lech ---
Still the same on 6.3.3 here :(
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496469
charly ghislain changed:
What|Removed |Added
CC||charlyghisl...@gmail.com
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=496469
John Kizer changed:
What|Removed |Added
CC||el...@seznam.cz
--- Comment #65 from John Kizer -
https://bugs.kde.org/show_bug.cgi?id=496469
Erik von Nastase changed:
What|Removed |Added
CC||e...@vonnasta.se
--- Comment #64 from Erik v
https://bugs.kde.org/show_bug.cgi?id=496469
Roman Pletka changed:
What|Removed |Added
CC||ro...@pletka.ch
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #63 from qethanmoore+...@gmail.com ---
(In reply to comment #48)
(In reply to comment #60)
I have upgraded my system today and this problem seems resolved. I have closed
my separate report, I hope it's resolved for you too.
Operating System
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #62 from Chan ---
Is anyone here facing this issue while running the 6.6 LTS kernel? I somehow
don't face this problem when I am running the 6.6 LTS kernel. I have run the
same setup (just the latest KDE 6.3.2 and Frameworks) for a week stra
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #61 from Chan ---
(In reply to Faidon Liambotis from comment #56)
> I, too, am suffering from an increased memory usage from kwin to the point
> of OOM, with resident memory often being at the 1.5G mark.
>
> However, unlike most (all?) repo
https://bugs.kde.org/show_bug.cgi?id=496469
qethanmoore+...@gmail.com changed:
What|Removed |Added
CC||qethanmoore+...@gmail.com
--- Commen
https://bugs.kde.org/show_bug.cgi?id=496469
Vlad Zabotinsky changed:
What|Removed |Added
CC|reiag...@gmail.com |zabotinski...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=496469
Paul May changed:
What|Removed |Added
CC||paul.may9...@gmail.com
Platform|Fedora RPM
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #58 from therealchubbypa...@gmail.com ---
I'm still seeing this issue on 6.3.2 consistently.
Archlinux: AMD onboard graphics + Nvidia 3070 laptop
My current workaround involves unplugging and reconnecting the external monitor
once in a whil
https://bugs.kde.org/show_bug.cgi?id=496469
tiagoslucas changed:
What|Removed |Added
CC||vigorous_freeload690@simple
|
https://bugs.kde.org/show_bug.cgi?id=496469
therealchubbypa...@gmail.com changed:
What|Removed |Added
Version|6.2.5 |6.3.2
CC|
https://bugs.kde.org/show_bug.cgi?id=496469
therealchubbypa...@gmail.com changed:
What|Removed |Added
CC||orza...@gmail.com
--- Comment #57
https://bugs.kde.org/show_bug.cgi?id=496469
Vlad Zabotinsky changed:
What|Removed |Added
CC|zabotinski...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=496469
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=496469
Faidon Liambotis changed:
What|Removed |Added
CC||parav...@debian.org
--- Comment #56 from Fai
https://bugs.kde.org/show_bug.cgi?id=496469
fabiodanielr...@hotmail.com changed:
What|Removed |Added
CC||fabiodanielr...@hotmail.com
--
Yo
https://bugs.kde.org/show_bug.cgi?id=496469
Zolv changed:
What|Removed |Added
CC||piotr.brzozow...@10code.pl
--- Comment #55 from Zolv --
https://bugs.kde.org/show_bug.cgi?id=496469
Eclipse changed:
What|Removed |Added
CC||ecli...@eclipseisoffline.xy
|
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #54 from Miroslav Jarý ---
Hey there,
same issue here. I have i5-13420H iGPU and RTX 4050 Laptop dGPU.
External monitor is connected via HDMI/Thunderbolt, and is operated by dGPU.
Issue occurs with or without sleep/hibernation.
Other sysinf
https://bugs.kde.org/show_bug.cgi?id=496469
Miroslav Jarý changed:
What|Removed |Added
CC||mira.j...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=496469
Serhii Hatsan changed:
What|Removed |Added
CC||serhiihat...@gmail.com
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=496469
Henrique Sant'Anna changed:
What|Removed |Added
CC||hsanta...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=496469
ojosdeser...@gmail.com changed:
What|Removed |Added
CC||ojosdeser...@gmail.com
--- Comment #53
https://bugs.kde.org/show_bug.cgi?id=496469
postix changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=496469
Robert-André Mauchin changed:
What|Removed |Added
CC||zebo...@gmail.com
--- Comment #51 from R
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #52 from Robert-André Mauchin ---
And I have this result:
journalctl --user-unit plasma-kwin_wayland --boot 0 | grep import
févr. 16 14:38:20 Cassini kwin_wayland[2651]: kwin_wayland_drm: chose egl
import with format AB30 and modifier 0
fé
https://bugs.kde.org/show_bug.cgi?id=496469
--- Comment #50 from Kubek4155 ---
I experience the same thing. For me it stops at 11GB memory usage. If I unplug
the monitor nothing happens, only when I plug it back whole Plasma restarts
(closing all my apps) but then the memory usage rises much fas
1 - 100 of 155 matches
Mail list logo
