https://bugs.kde.org/show_bug.cgi?id=428160
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |https://invent.kde.org/plas
| |ma/libksysguard/commit/9b51
| |61cb9a16eaad205631b2a4c382d
| |bbbe2072c
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #5 from David Edmundson <k...@davidedmundson.co.uk> ---
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 context to "this" so we should auto disconnect when the
Processes object is destroyed.
But Qt::DirectConnection means that is run in the runner thread.
It is possible to have a scenario where "this" is active when the
connection is made, but destroyed before we get to this line.
Related: bug 428048
But scoping the connect to Processes existing we would have leaked the
worker if Processes got destroyed whilst the worker was running.
M +8 -5 processcore/processes_linux_p.cpp
M +3 -8 processcore/read_procsmaps_runnable.cpp
M +1 -4 processcore/read_procsmaps_runnable.h
https://invent.kde.org/plasma/libksysguard/commit/9b5161cb9a16eaad205631b2a4c382dbbbe2072c
--
You are receiving this mail because:
You are watching all bug changes.
