https://bugs.kde.org/show_bug.cgi?id=428048
Patrick Silva changed:
What|Removed |Added
CC||omeru...@gmail.com
--- Comment #23 from
https://bugs.kde.org/show_bug.cgi?id=428048
Andrew M changed:
What|Removed |Added
CC||cmhea...@charter.net
--- Comment #22 from Andrew M
https://bugs.kde.org/show_bug.cgi?id=428048
Frank Kruger changed:
What|Removed |Added
CC||fkrue...@mailbox.org
--- Comment #21 from Frank
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #20 from Umbertho dellarojadecanariaportedelacruzkardinalll
---
Yes, that does it, thank you very much ;)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428048
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=428048
David Edmundson changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=428048
Nate Graham changed:
What|Removed |Added
Version Fixed In|5.20.2 |5.20.3
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=428048
David Edmundson changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=428048
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=428048
Bug Janitor Service changed:
What|Removed |Added
Status|REOPENED|ASSIGNED
--- Comment #17 from Bug
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #16 from David Edmundson ---
Aha, there's another obvious place for leaking.
QFile file{m_dir + QStringLiteral("smaps_rollup")};
if (!file.open(QIODevice::ReadOnly)) {
return;
}
We never hit emit finished(), no-one
https://bugs.kde.org/show_bug.cgi?id=428048
Riccardo Robecchi changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #14 from Umbertho dellarojadecanariaportedelacruzkardinalll
---
@David: 'more robustness' was a very kind way of understating my time-bomb ;)
commit 9b5161c does not seem to resolve the issue for me, I tried both master
and 5.20.2.
https://bugs.kde.org/show_bug.cgi?id=428048
David Edmundson changed:
What|Removed |Added
CC||cont...@snejugal.ru
--- Comment #13 from
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #12 from Riccardo Robecchi ---
(In reply to David Edmundson from comment #11)
> This is similar to the comment in #6, only with some more robustness on the
> syncing to the main thread.
>
> Lets see if this resolves everything
Thank you
https://bugs.kde.org/show_bug.cgi?id=428048
David Edmundson changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #10 from David Edmundson ---
Git commit 2d522614357d6dc5a5a7b738a35574f5d8f69da5 by David Edmundson.
Committed on 26/10/2020 at 17:25.
Pushed by davidedmundson into branch 'Plasma/5.20'.
Handle smap read result in the correct thread
We
https://bugs.kde.org/show_bug.cgi?id=428048
David Edmundson changed:
What|Removed |Added
Version Fixed In||5.20.2
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #9 from David Edmundson ---
Git commit 9b5161cb9a16eaad205631b2a4c382dbbbe2072c by David Edmundson.
Committed on 25/10/2020 at 23:00.
Pushed by davidedmundson into branch 'master'.
Handle smap read result in the correct thread
We set the
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #8 from David Edmundson ---
>how is it possible that some of us do and others don't experience these
>problems..
Based on what I think it is, probably the status bar or something else doing a
process list fetch.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=428048
David Edmundson changed:
What|Removed |Added
Priority|NOR |VHI
CC|
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #7 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/libksysguard/-/merge_requests/90
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #6 from Umbertho dellarojadecanariaportedelacruzkardinalll
---
So,
if a running system updates to a 'bad' version of libksysguard, the effects
will not show until the system is rebooted. If a bad version gets replaced with
a good
https://bugs.kde.org/show_bug.cgi?id=428048
Yaroslav Sidlovsky changed:
What|Removed |Added
CC||zawer...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #5 from Umbertho dellarojadecanariaportedelacruzkardinalll
---
In case the other bug report isn't monitored:
**
https://github.com/KDE/libksysguard/commit/40cb8d6acbb12e516c1d327a9b2574560adcb4ec
seems to be working without issues
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #4 from JanKusanagi ---
Still no issue here. KSysGuard running for 9h17m, using 32,6 MiB.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428048
Umbertho dellarojadecanariaportedelacruzkardinalll
changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #2 from Riccardo Robecchi ---
(In reply to JanKusanagi from comment #1)
> For contrast, I haven't experienced this problem after running KSysGuard for
> 3+ hours.
>
> The only difference in versions, apparently, is that here in Mageia I
https://bugs.kde.org/show_bug.cgi?id=428048
JanKusanagi changed:
What|Removed |Added
CC||jan-b...@gmx.co.uk
--- Comment #1 from
29 matches
Mail list logo
