https://bugs.kde.org/show_bug.cgi?id=419967
RJVB <rjvber...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rjvber...@gmail.com
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
Something already restarts kdeinit5 after a crash (or abort in a kioslave). Or
is that just
This isn't just a KIO problem: it's bound to happen to any project that
installs a kioslave.
The strange this is that I've just been tinkering with kio-gdrive, and I
haven't had to kill any kdeinit5 instance myself in order for it to use the
updated gdrive.so . I wrote that off to the fact that no `gdrive.so [kdeinit5]`
process remained after quitting Dolphin, but that can't be it if the parent
kdeinit5 process keeps the kioslave cached...
BTW, hadn't the idea been dropped to use a single, central "speed loader" that
keeps all shared libraries it has even seen loaded to speed up subsequent
launches? I seem to recall a discussion that this wasn't relevant anymore with
the modern fast storage?
--
You are receiving this mail because:
You are watching all bug changes.
