https://bugs.kde.org/show_bug.cgi?id=495974
Fushan Wen <qydwhotm...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/plasma-activities-stats/ |ma/plasma-activities-stats/
|-/commit/8a4731b811f322e93c |-/commit/1ddf939b53f883d0ba
|3c6e3e15ceda7214184620 |e1e1e01c44eac2c0af8ef5
--- Comment #8 from Fushan Wen <qydwhotm...@gmail.com> ---
Git commit 1ddf939b53f883d0bae1e1e01c44eac2c0af8ef5 by Fushan Wen.
Committed on 09/01/2025 at 13:05.
Pushed by fusionfuture into branch 'Plasma/6.3'.
Avoid nested event processing waiting for DBus queries.
If a plasma-activity-stats queries can reference the current activity
which involves loading from the running daemon. This is typically async
and cached.
If the daemon has not yet loaded or no event loop is running the current
code blocks to wait for a response.
The current code could work processEvents only handles the main thread
not the DBus thread. If we need to wait for a DBus result the right
action in this situation is a blocking DBus call.
Nested event processing is always a terrible anti-pattern and even if it
did work properly can lead to all sorts of issues elsewhere.
To avoid blocking calls in long-running applications which will re-run
queries when the activity changes anyway, it is guarded to only make
blocking calls for headless apps.
(cherry picked from commit 8a4731b811f322e93c3c6e3e15ceda7214184620)
b251ac83 Avoid nested event processing waiting for DBus queries.
Co-authored-by: David Edmundson <k...@davidedmundson.co.uk>
M +25 -8 src/activitiessync_p.cpp
https://invent.kde.org/plasma/plasma-activities-stats/-/commit/1ddf939b53f883d0bae1e1e01c44eac2c0af8ef5
--
You are receiving this mail because:
You are watching all bug changes.
