Re: KDevelop continuous activity?
René J.V. Bertin <[email protected]> Fri, 10 Apr 2020 15:03:20 +0200
| Newsgroups | gmane.comp.kde.users.kdevelop |
|---|---|
| Message-ID | <2644771.oPZ3lcyh2q@bola> |
On Thursday April 09 2020 20:51:13 Sven Brauch wrote: >> spend a lot of time creating the DUChain cleanup thread (surprising, in a >> session that only has TCL and patch files open?). > >What does "a lot of time" mean? Just starting the thread and notincing there's >nothing to do is already "a lot of time" compared to an otherwise idle >application. Is the frequency at which this happens in any way related to how much there is to do? In other words, couldn't (doesn't...) the cleanup mechanism - suspend itself after having done the last thing there was to do - get activated when something happens that will or could leave things to cleanup behind? I realise this may seem overkill (certainly if there's usually something to be done), but the principle *seems* very simple and cheap. (stopping the cursor blink when focus moves elsewhere is another case where you could question the actual gain, no?) R.