https://bugs.kde.org/show_bug.cgi?id=430003
Arjen Hiemstra <ahiems...@heimr.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Latest Commit| |https://invent.kde.org/plas
| |ma/ksysguard/commit/de20a4c
| |0259d255b95fabb4ccfc965f8c1
| |bf660d
Resolution|--- |FIXED
--- Comment #9 from Arjen Hiemstra <ahiems...@heimr.nl> ---
Git commit de20a4c0259d255b95fabb4ccfc965f8c1bf660d by Arjen Hiemstra.
Committed on 15/01/2021 at 13:06.
Pushed by ahiemstra into branch 'master'.
NetworkManager: Do not remove devices when their active connection changes
In certain cases, NetworkManager can go on a rampage sending active
connection change signals in very rapid succession. This results in
memory usage ballooning because lambda connections can not be unique.
Rather than destroying and recreating the NetworkManagerDevice objects
on active connection change, this changes things so that we only remove
them from the SensorContainer but keep the actual objects around. This
allows NetworkManagerDevice to track its active connection state,
removing the need for constant reconnects.
M +51 -22 plugins/global/network/NetworkManagerBackend.cpp
M +11 -1 plugins/global/network/NetworkManagerBackend.h
https://invent.kde.org/plasma/ksysguard/commit/de20a4c0259d255b95fabb4ccfc965f8c1bf660d
--
You are receiving this mail because:
You are watching all bug changes.
