https://bugs.kde.org/show_bug.cgi?id=376716
Igor Kushnir <igor...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |igor...@gmail.com
--- Comment #7 from Igor Kushnir <igor...@gmail.com> ---
(In reply to Artur from comment #6)
> Nope, cold start on the same _empty_ project on the next day - 10 seconds,
> then 2 sec! It's a death for any coder.
> Just have tried QT Creator, and actually it is a really great IDE! Open any
> C++ code without creating a project and it will complete _any_ piece of a
> code in a nanosecond! There are no seconds, but picoseconds maybe. It will
> be the best autocomplete mechanism for KDevelop.
My recent experience is the opposite. Qt Creator's completion for a
medium-sized project used to be satisfactory. It still froze occasionally, but
so does KDevelop's completion. There seemed to be a memory leak in Qt Creator's
clangd triggered by switching back and forth between project configurations.
After a recent update to Qt Creator 8, performance became so horrible that I
was forced to disable clangd and use Qt Creator's deprecated internal code
model fallback, which is less accurate but much faster and memory-efficient.
Lately I rarely experience completion slowness in KDevelop. Try creating a new
session. If that doesn't help, try deleting (or renaming/moving) all KDevelop's
settings, caches.
--
You are receiving this mail because:
You are watching all bug changes.
