https://bugs.kde.org/show_bug.cgi?id=470026

Adam Fontenot <adam.m.fontenot+...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|kactivitymanagerd pegs a    |kactivitymanagerd pegs a
                   |CPU core at 100% when       |CPU core at 100% when many
                   |downloading files from      |files are added to the
                   |Firefox                     |recently used list
                   |                            |(recently-used.xbel)
                   |                            |sequentially
          Component|Activities in general       |general
            Version|5.27.0                      |6.14.0
            Product|plasmashell                 |frameworks-kio
           Assignee|ivan.cu...@kde.org          |kio-bugs-n...@kde.org
           See Also|                            |https://bugs.kde.org/show_b
                   |                            |ug.cgi?id=468461,
                   |                            |https://bugs.kde.org/show_b
                   |                            |ug.cgi?id=501802
                 CC|                            |kdelibs-b...@kde.org
   Target Milestone|1.0                         |---

--- Comment #4 from Adam Fontenot <adam.m.fontenot+...@gmail.com> ---
I'm changing the title and moving this to reflect the generic nature of what I
take the issue to be.

Adding two "see also" links. There is an existing confirmed report that
*adding* an entry to the recently used list adds ~100 ms latency to the
application calling the KRecentDocument function. There's another confirmed
report related to the privacy issue I mentioned in a comment above: KDE adds
items to recently-used even when this is disabled in the settings.

I think *this* issue is about kactivitymanagerd using inotify on
recently-used.xbel and parsing it whenever the file is updated. This doesn't
add latency to operations like the other issue, but it can consume even more
CPU time (claiming a full core in this case) because it seems to reparse the
whole file whenever it changes.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to