https://bugs.kde.org/show_bug.cgi?id=238941
Michael Pyne <mp...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Michael Pyne <mp...@kde.org> ---
I've been able to reproduce that JuK does take a lot of I/O at start up
(because it loads the metadata for all music in its collection, including music
that may be present in default music folder paths).
I've progressively worked to address the worst bits of that, including by
moving the music scanner into a separate thread last year and by fixing a bug
causing music to be unnecessarily rescanned after first startup.
I think that should address much of what this bug is describing, although I'm
sure there's even better that could be done.
--
You are receiving this mail because:
You are watching all bug changes.
